Date: Tue, 30 May 2000 10:55:16 -0500
From: Mike Perry <[EMAIL PROTECTED]>
gdb 4.18 has no problems with this at all. (Yes, there is obviously
a race condition here, but that was part of my test). In 5.0, it
happens with or without the write race. Sometimes the process just
disapears instead of gdb claiming segfaults also. I've also seen
SIGILL's when I use my malloc debugger with this threaded
program. (http://fscked.org/proj/njamd.shtml)
Stock GDB 4.18 doesn't do any threads :-).
Anyway, this is a known limitation of GDB 5.0. It can't handle
exiting threads. There's also a bug in glibc 2.1.3 that's prevents it
from working correctly anyway. The glibc bug is already fixed in the
development version and will be in 2.2. I have a fix for the bug in
GDB too, but that one's still being reviewed by the GDB threads
maintainer. Hopefully it will be in the next release. You can find
it at the following URL:
http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00455.html
Without the glibc fix you might still encounter some occasional
problems if you're forking threads at a high speed.
Mark
