This is the mail archive of the
mailing list for the Cygwin project.
Re: Mysterious gdb behavior.
- From: "Paul Derbyshire" <derbyshire at globalserve dot net>
- To: cygwin at cygwin dot com
- Date: Sat, 27 Jul 2002 19:41:57 -0400
- Subject: Re: Mysterious gdb behavior.
- References: <3D42EC9B.2934.510208B4@localhost>
- Reply-to: derbyshire at globalserve dot net
On 27 Jul 2002 at 16:26, Nicholas Wourms wrote:
> --- Paul Derbyshire <firstname.lastname@example.org> 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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html