This is the mail archive of the
rda@sources.redhat.com
mailing list for the rda project.
RDA thread-db.c and thread exits / signal killings
- From: Jim Blandy <jimb at redhat dot com>
- To: Michael Snyder <msnyder at redhat dot com>
- Cc: rda at sources dot redhat dot com
- Date: 23 Sep 2004 11:11:58 -0500
- Subject: RDA thread-db.c and thread exits / signal killings
I'm working my way through the logic in rda/unix/thread-db.c. In
wait_all_threads, we walk the list of known threads and try to bring
them all into the 'waited' state by collecting the SIGSTOP signals
they've been sent, and stashing any other signals they've received in
the pending_events array.
It seems to me that, if more than one thread exits, or is killed by a
signal, that information will be lost: select_pending_event will
choose one event to report back to GDB, and then send_pending_signals
will empty out the pending_events array.
Is my reading right? Is this a bug, or is it not necessary to report
such things to GDB?