From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27992 invoked by alias); 23 Oct 2008 02:30:26 -0000 Received: (qmail 27984 invoked by uid 22791); 23 Oct 2008 02:30:25 -0000 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.31) with ESMTP; Thu, 23 Oct 2008 02:29:50 +0000 Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id m9N2TmWe012803 for ; Wed, 22 Oct 2008 19:29:48 -0700 Received: from wa-out-1112.google.com (wafm38.prod.google.com [10.114.189.38]) by wpaz13.hot.corp.google.com with ESMTP id m9N2Tkf6014204 for ; Wed, 22 Oct 2008 19:29:46 -0700 Received: by wa-out-1112.google.com with SMTP id m38so57165waf.14 for ; Wed, 22 Oct 2008 19:29:46 -0700 (PDT) Received: by 10.114.127.1 with SMTP id z1mr8216614wac.203.1224728986215; Wed, 22 Oct 2008 19:29:46 -0700 (PDT) Received: by 10.114.78.12 with HTTP; Wed, 22 Oct 2008 19:29:46 -0700 (PDT) Message-ID: <8ac60eac0810221929i3539ab2ck421e976a96633f2b@mail.gmail.com> Date: Thu, 23 Oct 2008 02:30:00 -0000 From: "Paul Pluzhnikov" To: "Bradshaw, James" Subject: Re: how can I dump out thread informations in gdb Cc: "ying lcs" , "gdb@sourceware.org" In-Reply-To: <9D7446CE06F3C647B7D17BA71E3AB9900464FC8F29@MAEXCEVS1.ets.enterasys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <568e62a40810221301t301c7d46o9e1d4446d54abc7f@mail.gmail.com> <8ac60eac0810221304n4c244406ja26b0be0e6653d5b@mail.gmail.com> <9D7446CE06F3C647B7D17BA71E3AB9900464FC8F29@MAEXCEVS1.ets.enterasys.com> 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: 2008-10/txt/msg00098.txt.bz2 On Wed, Oct 22, 2008 at 1:13 PM, Bradshaw, James wrote: > And when "info threads" gives the incorrect information, how exactly > do we address that problem? OP gave no indication that he gets incorrect information. > I gather from earlier posts, libthread_db > on the target must not be stripped in order to correctly view threads That is incorrect. AFAICT, libthread_db may be stripped (it must have dynamic symbol table intact; but strip normally doesn't touch dynamic symbol table anyway). However, on Linux libpthread.so.0 itself must not be stripped, or libthread_db will refuse to work with it. > at least on linux targets that have nptl support. Same applies to LinuxThreads. > Is that the only requirement? No: libthread_db.so.1 must match libpthread.so.0 (both must come from the same version of glibc). -- Paul Pluzhnikov