From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28743 invoked by alias); 26 Sep 2005 17:08:45 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 28720 invoked by uid 22791); 26 Sep 2005 17:08:39 -0000 Received: from ns1.lanforge.com (HELO www.lanforge.com) (66.165.47.210) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 26 Sep 2005 17:08:39 +0000 Received: from [71.112.207.5] (pool-71-112-207-5.sttlwa.dsl-w.verizon.net [71.112.207.5]) (authenticated bits=0) by www.lanforge.com (8.12.8/8.12.8) with ESMTP id j8QHFwo6008245; Mon, 26 Sep 2005 10:15:58 -0700 Message-ID: <43382B08.8080607@candelatech.com> Date: Mon, 26 Sep 2005 17:08:00 -0000 From: Ben Greear User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.10) Gecko/20050909 Fedora/1.7.10-1.3.2 MIME-Version: 1.0 To: Daniel Jacobowitz CC: gdb@sources.redhat.com Subject: Re: gdb does not show full backtrace for deadlocked pthread program. References: <4337A216.6050805@candelatech.com> <20050926132807.GA1436@nevyn.them.org> In-Reply-To: <20050926132807.GA1436@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-09/txt/msg00194.txt.bz2 Daniel Jacobowitz wrote: > On Mon, Sep 26, 2005 at 12:24:06AM -0700, Ben Greear wrote: > >>Hello! >> >>I have a program that uses pthreads and evidently has a >>nifty little thread deadlock. >> >>The interesting thing is that gdb will not show me the full >>backtrace of the deadlocked threads. Both tested system's running >>a slightly modified 2.6.11 kernel. The FC2 system is a dual-xeon with >>SMP kernel. The FC4 machine is a laptop with UP kernel. >>FC2's gdb doesn't even decode frame 3, but on FC4 I get this: >> >>[after attaching to deadlocked process] >> >>(gdb) thread apply all bt >> >>Thread 2 (Thread -1208132688 (LWP 9895)): >>#0 0xffffe410 in ?? () >>#1 0xb7fd50e8 in ?? () >>#2 0x00000002 in ?? () >>#3 0x004b4e7e in __lll_mutex_lock_wait () from /lib/libpthread.so.0 > > > GDB knows how to load symbols for the kernel DSO and backtrace from it. > It also knows how to load separate debug info packages, which I assume > Red Hat provides for libc. I would have expected the shipped GDB to do > this, but if not, try building your own from current CVS. If you > install the debug info packages and want to use them, you may need to > configure your own gdb with --prefix=/usr. The latest cvs did indeed print out useful stack traces. Would be lovely to have whatever magic makes that work in the more official releases! Thanks, Ben > -- Ben Greear Candela Technologies Inc http://www.candelatech.com