From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20281 invoked by alias); 1 May 2009 16:49:20 -0000 Received: (qmail 20024 invoked by uid 22791); 1 May 2009 16:49:16 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 01 May 2009 16:49:10 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 3DEF710721; Fri, 1 May 2009 16:49:08 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id BDAB410557; Fri, 1 May 2009 16:49:07 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1Lzvv8-0008P5-6y; Fri, 01 May 2009 12:49:06 -0400 Date: Fri, 01 May 2009 16:49:00 -0000 From: Daniel Jacobowitz To: Paul Pluzhnikov Cc: Eli Zaretskii , brobecker@adacore.com, teawater@gmail.com, tromey@redhat.com, bauerman@br.ibm.com, gdb-patches@sourceware.org Subject: Re: [patch][rfc] Allow GDB to search for the right libthread_db.so.1 Message-ID: <20090501164905.GA32287@caradoc.them.org> Mail-Followup-To: Paul Pluzhnikov , Eli Zaretskii , brobecker@adacore.com, teawater@gmail.com, tromey@redhat.com, bauerman@br.ibm.com, gdb-patches@sourceware.org References: <8ac60eac0904230001w1afd9179wcb76e1cfd7f3f386@mail.gmail.com> <8ac60eac0904291330m78b43c47p1cc9b8379e31e923@mail.gmail.com> <20090430185551.GB10734@adacore.com> <8ac60eac0904301211x245c8b7cp546042d832eb1fe@mail.gmail.com> <8ac60eac0904301618j61051e9du38b34afbc7ed64a3@mail.gmail.com> <83eiv9e1bb.fsf@gnu.org> <8ac60eac0905010849m7dc29bb5h171a703fa79d8b76@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8ac60eac0905010849m7dc29bb5h171a703fa79d8b76@mail.gmail.com> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-05/txt/msg00027.txt.bz2 On Fri, May 01, 2009 at 08:49:07AM -0700, Paul Pluzhnikov wrote: > On Fri, May 1, 2009 at 12:20 AM, Eli Zaretskii wrote: > > > Is thread debugging indeed completely impossible without libthread_db? > > Pretty much: GDB will not know about any threads other than the one > that is stopped or crashed; with LinuxThreads GDB will stop with SIG32 > all the time in unexpected places, etc. etc. > > Debugging experience for anyone but libpthread implementer will be > quite miserable. Have you tried this? I know it'll work better than that in gdbserver, at least if you run the application rather than attaching. We recognize thread creation events from the kernel. I don't remember what happens in GDB, though. -- Daniel Jacobowitz CodeSourcery