public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
* More bad backtraces through nanosleep
@ 2003-09-07 19:22 Daniel Jacobowitz
  2003-09-07 19:23 ` Daniel Jacobowitz
  0 siblings, 1 reply; 2+ messages in thread
From: Daniel Jacobowitz @ 2003-09-07 19:22 UTC (permalink / raw)
  To: gdb

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: More bad backtraces through nanosleep
  2003-09-07 19:22 More bad backtraces through nanosleep Daniel Jacobowitz
@ 2003-09-07 19:23 ` Daniel Jacobowitz
  0 siblings, 0 replies; 2+ messages in thread
From: Daniel Jacobowitz @ 2003-09-07 19:23 UTC (permalink / raw)
  To: gdb, libc-alpha

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-09-07 19:23 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-09-07 19:22 More bad backtraces through nanosleep Daniel Jacobowitz
2003-09-07 19:23 ` Daniel Jacobowitz

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).