Re: Can't attach to child using gdb-5.1.1 on Linux

[Jesse Marlin <jlm@compgen.com>]

Andrew Cagney writes:
 > > I have a process that forks a child.  If I try to attach to the
 > > child it reads the symbols and shows an accurate stack trace, but when
 > > I set a breakpoint and try to continue I get the following:
 > > 
 > > (gdb) c
 > > Continuing.
 > > lin-lwp.c:1003: gdb-internal-error: lin_lwp_wait: Assertion `WIFSTOPPED (status) && WSTOPSIG (status) == SIGSTOP' failed.
 > > An internal GDB error was detected.  This may make further
 > > debugging unreliable.  Continue this debugging session? (y or n) n
 > > 
 > > Create a core file containing the current state of GDB? (y or n) n
 > > 
 > > Inferior GDB exited abnormally with code 1
 > > 
 > > 
 > > I answered yes to the above also, but it did not improve the situation.  Has
 > > anybody seen this behvior before.  I am using gcc-2.95.3 for compilation.
 > 
 > (not sure if someone has responded to this)

No this is first.

 > 
 > The first thing to do is get a more recent GDB from:

I have been using gdb-5.1.1.  More recent as in the current CVS?
Thanks for the response.

 > 
 > 	http://sources.redhat.com/gdb/current/
 > 
 > many problems have been fixed and if this problem still occures things 
 > have been narrowed down a bit.
 > 
 > Andrew
 >