From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21698 invoked by alias); 5 Apr 2009 20:11:32 -0000 Received: (qmail 21679 invoked by uid 22791); 5 Apr 2009 20:11:30 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout7.012.net.il (HELO mtaout7.012.net.il) (84.95.2.19) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 05 Apr 2009 20:11:21 +0000 Received: from conversion-daemon.i-mtaout7.012.net.il by i-mtaout7.012.net.il (HyperSendmail v2007.08) id <0KHN00C008CHAV00@i-mtaout7.012.net.il> for gdb@sourceware.org; Sun, 05 Apr 2009 23:10:08 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.139.199]) by i-mtaout7.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KHN00LMV9CTQF70@i-mtaout7.012.net.il>; Sun, 05 Apr 2009 23:10:06 +0300 (IDT) Date: Sun, 05 Apr 2009 20:36:00 -0000 From: Eli Zaretskii Subject: Re: improved thread id reporting In-reply-to: <8ac60eac0904051221w1ed36cf2gd876570920239442@mail.gmail.com> To: Paul Pluzhnikov Cc: drow@false.org, mark.kettenis@xs4all.nl, dje@google.com, gdb@sourceware.org Reply-to: Eli Zaretskii Message-id: <83tz52c197.fsf@gnu.org> References: <20090404184604.8524C1C759C@localhost> <200904041904.n34J4UXV013513@brahms.sibelius.xs4all.nl> <20090404192132.GA28232@caradoc.them.org> <834ox4cfz2.fsf@gnu.org> <20090404212114.GA3077@caradoc.them.org> <831vs7dcc1.fsf@gnu.org> <8ac60eac0904042047q39429d61laed945cf17606759@mail.gmail.com> <83vdpjarmx.fsf@gnu.org> <8ac60eac0904051221w1ed36cf2gd876570920239442@mail.gmail.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00066.txt.bz2 > Date: Sun, 5 Apr 2009 12:21:47 -0700 > From: Paul Pluzhnikov > Cc: drow@false.org, mark.kettenis@xs4all.nl, dje@google.com, > gdb@sourceware.org > > On Sun, Apr 5, 2009 at 11:21 AM, Eli Zaretskii wrote: > > > > Would it be a good idea to mention this in the manual? > > Something like this: Yes, but I also thought about telling what you and Daniel mentioned: that the thread ID is useful when you are debugging a deadlock etc. Thanks.