Re: improved thread id reporting

[Eli Zaretskii <eliz at gnu dot org>]

> 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?