From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-34129-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 27996 invoked by alias); 5 Apr 2009 18:23:21 -0000
Received: (qmail 27986 invoked by uid 22791); 5 Apr 2009 18:23:21 -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 mtaout2.012.net.il (HELO mtaout2.012.net.il) (84.95.2.4)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 05 Apr 2009 18:23:15 +0000
Received: from conversion-daemon.i_mtaout2.012.net.il by i_mtaout2.012.net.il (HyperSendmail v2004.12) id <0KHN00I0041JXI00@i_mtaout2.012.net.il> for gdb@sourceware.org; Sun, 05 Apr 2009 21:23:12 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([84.228.139.199]) by i_mtaout2.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KHN004CV4ENQI80@i_mtaout2.012.net.il>; Sun, 05 Apr 2009 21:23:12 +0300 (IDT)
Date: Sun, 05 Apr 2009 18:50:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: improved thread id reporting
In-reply-to: <8ac60eac0904042047q39429d61laed945cf17606759@mail.gmail.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: drow@false.org, mark.kettenis@xs4all.nl, dje@google.com, gdb@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83vdpjarmx.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>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2009-04/txt/msg00063.txt.bz2

> Date: Sat, 4 Apr 2009 20:47:56 -0700
> From: Paul Pluzhnikov <ppluzhnikov@google.com>
> Cc: Daniel Jacobowitz <drow@false.org>, mark.kettenis@xs4all.nl,
>         dje@google.com, gdb@sourceware.org
> 
> On Sat, Apr 4, 2009 at 8:11 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> Date: Sat, 4 Apr 2009 17:21:14 -0400
> >> From: Daniel Jacobowitz <drow@false.org>
> >> Cc: mark.kettenis@xs4all.nl, dje@google.com, gdb@sourceware.org
> >>
> >> On native Linux, they're the same as pthread_self would return.
> >
> > And how's that useful?
> 
> Sometimes that's very useful.
> 
> One example is where thread has performed some logging with
> its pthread_self, and you are now trying to figure out which
> thread that was.
> 
> Another is when you are debugging a deadlock, and want to know
> who is waiting on the given lock (thread ids of waiters are
> stored somewhere in mutex_t, IIRC).

Thanks for explaining.

Would it be a good idea to mention this in the manual?