Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Inconsistent behavior for Win32 executable: starting from bash vs. starting from cmd.exe
Date:	Mon, 11 Jul 2005 16:39:22 +0100
MIME-Version:	1.0
In-Reply-To:	<Pine.GSO.4.61.0507111118450.7597@slinky.cs.nyu.edu>
Message-ID:	<SERRANO1YBTUA93Nii500000490@SERRANO.CAM.ARTIMI.COM>

----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/

- Raw text -