From: Daniel Jacobowitz <drow@false.org>
To: Richard van der Hoff <richardv@mxtelecom.com>
Cc: gdb@sourceware.org
Subject: Re: Backtrace not working from within nanosleep
Date: Tue, 06 Mar 2007 16:58:00 -0000 [thread overview]
Message-ID: <20070306165840.GA6029@caradoc.them.org> (raw)
In-Reply-To: <45ED99E9.8050404@mxtelecom.com>
On Tue, Mar 06, 2007 at 04:42:17PM +0000, Richard van der Hoff wrote:
> The stack looks fine - it just looks like gdb can't unwind it. Any ideas
> what might be the problem here?
>
> I have:
>
> Linux kernel 2.4.26
> GNU gdb 6.6
> gcc (GCC) 3.3.4
> glibc-2.3.6
LinuxThreads, presumably, since this is 2.4.x. That means it is
fairly likely that you do not have unwind tables for nanosleep, so GDB
is unable to reason its way out.
I believe this is fixed if you use glibc 2.5, but I'm not completely
sure of that.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-06 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 16:42 Richard van der Hoff
2007-03-06 16:58 ` Daniel Jacobowitz [this message]
2007-03-06 17:10 ` Richard van der Hoff
2007-03-06 17:12 ` Daniel Jacobowitz
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=20070306165840.GA6029@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=richardv@mxtelecom.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