* RDA thread-db.c and thread exits / signal killings
@ 2004-09-23 16:13 Jim Blandy
0 siblings, 0 replies; only message in thread
From: Jim Blandy @ 2004-09-23 16:13 UTC (permalink / raw)
To: Michael Snyder; +Cc: rda
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?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-09-23 16:13 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-09-23 16:13 RDA thread-db.c and thread exits / signal killings Jim Blandy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).