From: Kevin Buettner <kevinb@redhat.com>
To: rda@sources.redhat.com
Subject: Re: [RFC] Improve performance of multi-threaded debugging
Date: Fri, 04 Nov 2005 21:16:00 -0000 [thread overview]
Message-ID: <20051104141635.7c7b611f@ironwood.lan> (raw)
In-Reply-To: <20050914150439.5a86df49@ironwood.lan>
On Wed, 14 Sep 2005 15:04:39 -0700
Kevin Buettner <kevinb@redhat.com> wrote:
> * thread-db.c (ALWAYS_UPDATE_THREAD_LIST): Define to be 0.
> (handle_thread_db_event): Update thread list upon receipt of
> TD_CREATE or TD_DEATH events.
> (thread_db_check_child_state): Potentially disable, depending upon
> value of ALWAYS_UPDATE_THREAD_LIST, the thread list update.
> (thread_db_check_child_state): Update thread list for signal based
> event model too.
While preparing a patch for some recent work that I've done on RDA, I
noticed that I had not yet committed the above changes. They're in now.
Kevin
prev parent reply other threads:[~2005-11-04 21:16 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
2005-09-17 0:19 ` Jim Blandy
2005-11-04 21:16 ` Kevin Buettner [this message]
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=20051104141635.7c7b611f@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).