From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com, libc-alpha@sources.redhat.com
Subject: Re: More bad backtraces through nanosleep
Date: Sun, 07 Sep 2003 19:23:00 -0000 [thread overview]
Message-ID: <20030907192345.GA4141@nevyn.them.org> (raw)
In-Reply-To: <20030907192232.GA3951@nevyn.them.org>
Er, ah, I meant to send this to libc-alpha also of course.
On Sun, Sep 07, 2003 at 03:22:32PM -0400, Daniel Jacobowitz wrote:
> This is a little unfortunate...
>
> Glibc with NPTL uses DWARF-2 unwind information to describe syscall
> wrappers, because the NPTL implementation of cancellation uses dwarf2
> unwinding. However, glibc with LinuxThreads does not. So if you're running
> a multi-threaded LinuxThreads application, when we hit a syscall we're
> likely to get completely lost. We can't reasonably expect GDB's prologue
> unwinder to figure out nanosleep; the function has no prologue, and then
> pushes things onto the stack inside CENABLE/CDISABLE.
>
> Libc folks, would there be any disadvantages besides space to adding unwind
> info to the cancellable syscall wrappers in LT also? How would you feel
> about such a patch?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-09-07 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-07 19:22 Daniel Jacobowitz
2003-09-07 19:23 ` Daniel Jacobowitz [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=20030907192345.GA4141@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=libc-alpha@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