From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6166 invoked by alias); 23 Apr 2010 07:51:52 -0000 Received: (qmail 6146 invoked by uid 22791); 23 Apr 2010 07:51:47 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from relay-pt3.poste.it (HELO relay-pt3.poste.it) (62.241.4.129) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 23 Apr 2010 07:51:41 +0000 Received: from ssabatini.reitek.com (93.63.174.176) by relay-pt3.poste.it (8.5.121.01) (authenticated as stefano.sabatini-lala@poste.it) id 4BD0D53B0000E9BD for gdb@sources.redhat.com; Fri, 23 Apr 2010 09:51:38 +0200 Received: from stefano by ssabatini.reitek.com with local (Exim 4.71) (envelope-from ) id 1O5Dfj-0000rj-K1 for gdb@sources.redhat.com; Fri, 23 Apr 2010 09:51:35 +0200 Date: Fri, 23 Apr 2010 07:51:00 -0000 From: Stefano Sabatini To: gdb Mailing List Subject: Re: pthread_t ids of threads not showed by "thread info" Message-ID: <20100423075135.GA3297@geppetto> Mail-Followup-To: gdb Mailing List References: <20100422151855.GA3128@geppetto> <20100422154404.GB3128@geppetto> <20100422165924.GA1109@host0.dyn.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100422165924.GA1109@host0.dyn.jankratochvil.net> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2010-04/txt/msg00093.txt.bz2 On Thursday 2010-04-22 18:59:24 +0200, Jan Kratochvil wrote: > On Thu, 22 Apr 2010 17:44:04 +0200, Stefano Sabatini wrote: > > The difference between the first and the second scenario is that the > > first output was issued debugging a core, the second one by running a > > process through gdb run. > > Yes, IIRC GDB does not use linux-thread-db.c (libthread_db) for core files. > `info threads' displays LWPs (and not real threads) in such case. > > > > May be possible that it is not possible to extract the pthread_t > > info from a core file? > > LWPs do not have associated pthread_t. > > > Can you explain why? > > IIRC I tried once to add linux-thread-db.c for core files but for some reason > it was not completely trivial and I rather debugged the specific case by hand > iterating some pthread_t structures for that crash. Could you elaborate on that? I mean are you saying that it is possible but currently unimplemented? I'm in a situation where I need that feature (having a core with a deadlock, I know which are the pthread_t of the involved threads but I cannot associate them with the corresponding gdb threads), so I'll file a feature-request or maybe will try myself to implement the feature. > Regards, Thanks, regards.