Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<20020727045007.47096.qmail@web10105.mail.yahoo.com>
Date:	Sat, 27 Jul 2002 06:50:07 +0200 (CEST)
From:	=?iso-8859-1?q?Sylvain=20Petreolle?= <spetreolle AT yahoo DOT fr>
Subject:	Re: Mysterious gdb behavior.
To:	derbyshire AT globalserve DOT net, cygwin AT cygwin DOT com
Cc:	cygwin AT cygwin DOT com
In-Reply-To:	<3D41C7D2.30094.4C8A5635@localhost>
MIME-Version:	1.0

> Now why is it suddenly complaining that perfectly good executables 
> are bad? Or if the executables really are bad, why the hell do they 
> *work* (at least, run and crash rather than fail to run at all) when 
> launched from bash? Bash and gdb presumably spawn processes in the 
> same way, however unix does that, and with the cygwin compatibility 
> layer between that and however Windows spawns processes.
> 
Did you try this with several executable files ?
The error could come from a single hosed file.

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -