From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23606 invoked by alias); 5 Apr 2009 03:48:11 -0000 Received: (qmail 23584 invoked by uid 22791); 5 Apr 2009 03:48:10 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 05 Apr 2009 03:48:03 +0000 Received: from spaceape23.eur.corp.google.com (spaceape23.eur.corp.google.com [172.28.16.75]) by smtp-out.google.com with ESMTP id n353lxED027349 for ; Sun, 5 Apr 2009 04:47:59 +0100 Received: from rv-out-0506.google.com (rvbf6.prod.google.com [10.140.82.6]) by spaceape23.eur.corp.google.com with ESMTP id n353lumG028904 for ; Sat, 4 Apr 2009 20:47:57 -0700 Received: by rv-out-0506.google.com with SMTP id f6so1470285rvb.53 for ; Sat, 04 Apr 2009 20:47:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.254.2 with SMTP id b2mr828772wfi.287.1238903276666; Sat, 04 Apr 2009 20:47:56 -0700 (PDT) In-Reply-To: <831vs7dcc1.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> Date: Sun, 05 Apr 2009 07:19:00 -0000 Message-ID: <8ac60eac0904042047q39429d61laed945cf17606759@mail.gmail.com> Subject: Re: improved thread id reporting From: Paul Pluzhnikov To: Eli Zaretskii Cc: Daniel Jacobowitz , mark.kettenis@xs4all.nl, dje@google.com, gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-System-Of-Record: true 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/msg00059.txt.bz2 On Sat, Apr 4, 2009 at 8:11 PM, Eli Zaretskii wrote: >> Date: Sat, 4 Apr 2009 17:21:14 -0400 >> From: Daniel Jacobowitz >> 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). -- Paul Pluzhnikov