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
From: "Paul Derbyshire" <derbyshire AT globalserve DOT net>
To: cygwin AT cygwin DOT com
Date: Sat, 27 Jul 2002 19:41:57 -0400
MIME-Version: 1.0
Subject: Re: Mysterious gdb behavior.
Reply-to: derbyshire AT globalserve DOT net
Message-ID: <3D42F785.22663.512CA9BB@localhost>
In-reply-to: <20020727232636.54019.qmail@web21010.mail.yahoo.com>
References: <3D42EC9B DOT 2934 DOT 510208B4 AT localhost>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

On 27 Jul 2002 at 16:26, Nicholas Wourms wrote:

> 
> --- Paul Derbyshire <derbyshire AT globalserve DOT net> wrote:
> > On 27 Jul 2002 at 6:50, Sylvain Petreolle wrote:
> > 
> > > 
> > > > 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.
> > 
> > $ gdb -nw hw
> > GNU gdb 5.0 (20010428-3)
> > Copyright 2001 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Pu
> > welcome to change it and/or distribute copies of it
> > Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB.  Type "sho
> > This GDB was configured as "i686-pc-cygwin"...
> > (gdb) run
> > Starting program: /home/Paul Derbyshire/antheria/hw.exe
> > Error creating process /home/Paul Derbyshire/antheria/hw.exe,
>                                ^^^^^^^^^^^^^^^
> *SIGH*  Looks like someone didn't read the FAQ...

Excuse me? Should I not be trying to gdb executables under /home, or 
something?

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