public inbox for
 help / color / mirror / Atom feed
From: Jim Blandy <>
To: Michael Snyder <>
Subject: RDA thread-db.c and thread exits / signal killings
Date: Thu, 23 Sep 2004 16:13:00 -0000	[thread overview]
Message-ID: <vt2pt4dezht.fsf@zenia.home> (raw)

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?

                 reply	other threads:[~2004-09-23 16:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vt2pt4dezht.fsf@zenia.home \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).