From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3815 invoked by alias); 29 Apr 2008 18:17:39 -0000 Received: (qmail 3805 invoked by uid 22791); 29 Apr 2008 18:17:38 -0000 X-Spam-Check-By: sourceware.org Received: from mx3.redhat.com (HELO mx3.redhat.com) (66.187.233.32) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 29 Apr 2008 18:17:18 +0000 Received: from mail.codesourcery.com (mail.codesourcery.com [65.74.133.4]) by mx3.redhat.com (8.13.8/8.13.8) with ESMTP id m3TIGpCA004490 for <"gdb-patches@sources"@redhat.com>; Tue, 29 Apr 2008 14:16:52 -0400 Received: (qmail 24757 invoked from network); 29 Apr 2008 18:16:46 -0000 Received: from unknown (HELO localhost) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 29 Apr 2008 18:16:46 -0000 From: Vladimir Prus To: Nick Roberts Subject: Re: [RFA] Implement thread death notification. Date: Tue, 29 Apr 2008 20:07:00 -0000 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) Cc: "gdb-patches@sources"@redhat.com References: <18452.16686.528039.84732@kahikatea.snap.net.nz> In-Reply-To: <18452.16686.528039.84732@kahikatea.snap.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200804292216.45231.vladimir@codesourcery.com> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-04/txt/msg00670.txt.bz2 On Sunday 27 April 2008 13:02:38 Nick Roberts wrote: > > > We now have the 'thread-created' MI notification. This patch adds a > > 'thread-exited' notification to match. Are non-MI bits of this > > patch OK? > > When I suggested this previously, we said: > > > > I'm not sure what you mean. If I run Gdb normally with a multi-threaded > > > application, I get: > > > > > > [New Thread -1210639472 (LWP 7235)] > > > > > > when a thread is created and: > > > > > > [Thread -1210639472 (LWP 7235) exited] > > > > > > when it is terminated. > > > > At which point, and where in code is that message printed? It is > > printed by linux-thread-db.c:detach_thread, so it's not good for > > generic code. And generic code will hold on to thread until > > "info thread". It's not very good if you need to issue "info thread" > > to get notifications about exited thread. > > > > So, thread.c and its interaction with linux-thread-db.c have to > > be fixed. > > Does it mean that this has now been fixed? No. However, it seems useful to provide this notification initially for Linux. - Volodya