2.4.4: thread dumping core

["Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>]

Hi,

I wonder whether the kernel does the right thing if a thread causes a 
segmentation violation: Currently it seems the other LWPs just 
continue. However in practice this means that the application does not 
work reliable when one thread went away.

I suggest to terminate all LWPs if one receives a fatal signal.

I wasn't successful debugging the beast:

Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libpthread.so.0...done.
rw_common (): write: Success.

warning: unable to set global thread event mask
[New Thread 1024 (LWP 10566)]
Error while reading shared library symbols:
attach_thread: No such process.
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
#0  0x4005e0a6 in sigsuspend () from /lib/libc.so.6
(gdb) bt
#0  0x4005e0a6 in sigsuspend () from /lib/libc.so.6
#1  0x4002496c in sigwait () from /lib/libpthread.so.0
#2  0x804da47 in mi_signal_thread ()
#3  0x40021ba3 in pthread_start_thread () from /lib/libpthread.so.0


Opinions?

Ulrich