From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1369 invoked by alias); 11 Jun 2008 14:58:52 -0000 Received: (qmail 1360 invoked by uid 22791); 11 Jun 2008 14:58:52 -0000 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.31) with ESMTP; Wed, 11 Jun 2008 14:58:34 +0000 Received: from spaceape10.eur.corp.google.com (spaceape10.eur.corp.google.com [172.28.16.144]) by smtp-out.google.com with ESMTP id m5BEwKh7027113 for ; Wed, 11 Jun 2008 15:58:20 +0100 Received: from wa-out-1112.google.com (wafk22.prod.google.com [10.114.187.22]) by spaceape10.eur.corp.google.com with ESMTP id m5BEwJNd003303 for ; Wed, 11 Jun 2008 15:58:19 +0100 Received: by wa-out-1112.google.com with SMTP id k22so2492065waf.20 for ; Wed, 11 Jun 2008 07:58:18 -0700 (PDT) Received: by 10.114.151.13 with SMTP id y13mr6666407wad.134.1213196298616; Wed, 11 Jun 2008 07:58:18 -0700 (PDT) Received: by 10.114.254.4 with HTTP; Wed, 11 Jun 2008 07:58:18 -0700 (PDT) Message-ID: Date: Wed, 11 Jun 2008 14:58:00 -0000 From: "Doug Evans" To: "Srinivas Murthy" Subject: Re: gdb doesnt show nptl threads Cc: gdb@sourceware.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: 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-06/txt/msg00093.txt.bz2 On Wed, Jun 11, 2008 at 12:19 AM, Srinivas Murthy wrote: > Hi, > I have the following setup: > gdb6.6 built using a 64b glibc w/ nptl enabled > 64b glibc - 2.3.6 (nptl enabled) > > When I use gdb on a sample multi-threaded (nptl) app, I cant get any > thread specific gdb cmds to work. > > For ex. info threads shows only one thread (the main thread). > > Any idea what might be going wrong? Unlikely, but one thing that could explain this is the glibc you're using is a hand-made one installed in some place other than /lib64. gdb will only look for libthread_db in a few specific places. A copy of the session log from the start up until the error could help diagnosis.