gdb crashes when process goes away?

[David N. Welton]

@ashland [~] $ gdb --version
GNU gdb 5.3-debian

@ashland [~] $ uname -a
Linux ashland 2.4.20 #20 Tue Mar 4 16:13:14 PST 2003 ppc unknown unknown 
GNU/Linux

I *think* what is happening is that I attached to a process that was
in the middle of going away:

In the apache logs:
[Tue May 13 19:42:57 2003] [notice] child pid 18494 exit signal Segmentation 
fault (11)
[Tue May 13 19:42:59 2003] [notice] child pid 18493 exit signal Segmentation 
fault (11)

ashland:~# gdb apache.dbg 18492

...

Reading symbols from /lib/libpthread.so.0...done.
[New Thread 16384 (LWP 18465)]
Error while reading shared library symbols:
Can't attach LWP 18465: No such process

...

(gdb) cont
Continuing.
../../gdb/lin-lwp.c:1103: 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.  Quit this debugging session? (y or n) y

The process I'm debugging is a 'mess'.  Apache compiled to load shared
modules.  The shared module that is probably mucking things up is a
mod_rivet.so compiled against a threaded tcl8.4.

I *am* able to reproduce this bug reliably, so let me know if there
are other things I can do to chase it down.

-- 
David N. Welton
   Consulting: http://www.dedasys.com/
     Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
   Apache Tcl: http://tcl.apache.org/