From: Kevin Buettner <kevinb@redhat.com>
To: rda@sources.redhat.com
Subject: Re: [RFC] Improve performance of multi-threaded debugging
Date: Fri, 16 Sep 2005 20:49:00 -0000 [thread overview]
Message-ID: <20050916134939.5ad3fe5f@ironwood.lan> (raw)
In-Reply-To: <m38xxwydci.fsf@alligator.red-bean.com>
On Fri, 16 Sep 2005 13:19:57 -0700
Jim Blandy <jimb@redhat.com> wrote:
>
> Kevin Buettner <kevinb@redhat.com> writes:
> > The only fly in the ointment is that the signal based event model only
> > knows about thread creation, but not about thread death. So it won't
> > catch thread death until some new thread is created. I'm not sure
> > what the implications of this are in practice.
>
> Even in the signal-based model, we're attached to all the threads, so
> we should get a wait status via lwp_pool_waitpid. Isn't that working?
It probably does, but do not know for certain.
I saw that the thread list was getting fetched on every status check. My
assumption was that there was some good reason for this to occur and revised
the code so that it would only happen when so informed by the event model.
What I did not investigate is whether the thread refetch ever really needs
to happen at all.
Kevin
next prev parent reply other threads:[~2005-09-16 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 22:04 Kevin Buettner
2005-09-14 22:09 ` Daniel Jacobowitz
2005-09-14 22:31 ` Kevin Buettner
2005-09-16 20:13 ` Jim Blandy
2005-09-16 20:20 ` Jim Blandy
2005-09-16 20:49 ` Kevin Buettner [this message]
2005-09-17 0:19 ` Jim Blandy
2005-11-04 21:16 ` Kevin Buettner
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050916134939.5ad3fe5f@ironwood.lan \
--to=kevinb@redhat.com \
--cc=rda@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).