From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18391 invoked by alias); 4 Apr 2009 22:35:03 -0000 Received: (qmail 18382 invoked by uid 22791); 4 Apr 2009 22:35:02 -0000 X-SWARE-Spam-Status: No, hits=-1.9 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.45.13) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 04 Apr 2009 22:34:57 +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 n34MYsL2015269 for ; Sat, 4 Apr 2009 15:34:55 -0700 Received: from rv-out-0506.google.com (rvbf6.prod.google.com [10.140.82.6]) by spaceape23.eur.corp.google.com with ESMTP id n34MYqSF000707 for ; Sat, 4 Apr 2009 15:34:53 -0700 Received: by rv-out-0506.google.com with SMTP id f6so1735300rvb.45 for ; Sat, 04 Apr 2009 15:34:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.201.8 with SMTP id y8mr1311674rvf.97.1238884492345; Sat, 04 Apr 2009 15:34:52 -0700 (PDT) In-Reply-To: <20090404212114.GA3077@caradoc.them.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> Date: Sun, 05 Apr 2009 01:11:00 -0000 Message-ID: Subject: Re: improved thread id reporting From: Doug Evans To: Eli Zaretskii , mark.kettenis@xs4all.nl, dje@google.com, gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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/msg00055.txt.bz2 On Sat, Apr 4, 2009 at 2:21 PM, Daniel Jacobowitz wrote: > On Sat, Apr 04, 2009 at 11:37:53PM +0300, Eli Zaretskii wrote: >> > Date: Sat, 4 Apr 2009 15:21:32 -0400 >> > From: Daniel Jacobowitz >> > Cc: dje@google.com, gdb@sourceware.org >> > >> > I think the existing IDs are quite handy. >> >> What for? =A0If they are useful, we should probably tell in the manual >> how to use them. > > Their meaning is platform-specific; they're usually something that > will be recognized by programmers familiar with the OS in question. > On native Linux, they're the same as pthread_self would return. > I think they're just LWP IDs when using gdbserver; we had trouble > passing NPTL thread IDs over the remote protocol. I checked gdbserver on linux. (gdb) i thr [New Thread 30119.30125] 5 Thread 30119.30125 0xf7f27748 in clone () from /usr/lib/libc.so.6 * 4 Thread 30119.30124 thread_entry (unused=3D0x0) at ../../../../src/gdb/testsuite/gdb.threads/interrupted-hand-call.c:77 3 Thread 30119.30121 incr_thread_count () at ../../../../src/gdb/testsuite/gdb.threads/interrupted-hand-call.c:44 2 Thread 30119.30120 0xf7fbedbc in __pthread_enable_asynccancel () from /usr/lib/libpthread.so.0 1 Thread 30119.30119 0xf7f27748 in clone () from /usr/lib/libc.so.6 Kinda nice.