From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rda-return-361-listarch-rda=sources.redhat.com@sources.redhat.com>
Received: (qmail 31058 invoked by alias); 16 Sep 2005 20:20:53 -0000
Mailing-List: contact rda-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:rda-subscribe@sources.redhat.com>
List-Post: <mailto:rda@sources.redhat.com>
List-Help: <mailto:rda-help@sources.redhat.com>, <http://sources.redhat.com/lists.html#faqs>
Sender: rda-owner@sources.redhat.com
Received: (qmail 31044 invoked by uid 22791); 16 Sep 2005 20:20:49 -0000
Received: from nat-pool-rdu.redhat.com (HELO devserv.devel.redhat.com) (66.187.233.202)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 16 Sep 2005 20:20:49 +0000
Received: from alligator.red-bean.com.redhat.com (vpn26-3.sfbay.redhat.com [172.16.26.3])
	by devserv.devel.redhat.com (8.12.11/8.12.11) with ESMTP id j8GKKkex011794;
	Fri, 16 Sep 2005 16:20:47 -0400
To: Kevin Buettner <kevinb@redhat.com>
Cc: rda@sources.redhat.com
Subject: Re: [RFC] Improve performance of multi-threaded debugging
References: <20050914150439.5a86df49@ironwood.lan>
From: Jim Blandy <jimb@redhat.com>
Date: Fri, 16 Sep 2005 20:20:00 -0000
In-Reply-To: <20050914150439.5a86df49@ironwood.lan> (Kevin Buettner's message of "Wed, 14 Sep 2005 15:04:39 -0700")
Message-ID: <m38xxwydci.fsf@alligator.red-bean.com>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-SW-Source: 2005-q3/txt/msg00007.txt.bz2


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?