This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Inconsistent behavior for Win32 executable: starting from bash vs. starting from cmd.exe
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Mon, 11 Jul 2005 16:39:22 +0100
- Subject: RE: Inconsistent behavior for Win32 executable: starting from bash vs. starting from cmd.exe
----Original Message----
>From: Igor Pechtchanski
>Sent: 11 July 2005 16:26
> First thing I'd do is prepend 'c:\cygwin\bin' to the PATH in cmd.exe and
> see if that reproduces the problem in cmd.exe.
I couldn't reproduce this problem at all, using either g++ or msvc,
running from either bash or cmd. I suspect there's an underlying problem
with the network and the error code returned is misleading.
> Would
>
> UNIVERSAL_NAME_INFO szBuff;
> UNIVERSAL_NAME_INFO *puni = &szBuff;
>
> work better? I'm not familiar with UNIVERSAL_NAME_INFO, but the above
> assumes it's no larger than 2k in size.
No it doesn't. Check cbBuff.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/