From: Ben Greear <greearb@candelatech.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: gdb does not show full backtrace for deadlocked pthread program.
Date: Mon, 26 Sep 2005 17:08:00 -0000 [thread overview]
Message-ID: <43382B08.8080607@candelatech.com> (raw)
In-Reply-To: <20050926132807.GA1436@nevyn.them.org>
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 <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2005-09-26 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 7:24 Ben Greear
2005-09-26 13:28 ` Daniel Jacobowitz
2005-09-26 17:08 ` Ben Greear [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43382B08.8080607@candelatech.com \
--to=greearb@candelatech.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).