[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[libunwind] Fwd: libunwind issue on x86
From: |
David Mosberger-Tang |
Subject: |
[libunwind] Fwd: libunwind issue on x86 |
Date: |
Thu, 15 Sep 2005 13:26:40 -0700 |
Resend, now that I'm subscribed again...
--david
---------- Forwarded message ----------
From: David Mosberger-Tang <address@hidden>
Date: Sep 14, 2005 3:42 PM
Subject: Re: libunwind issue on x86
To: address@hidden
Cc: address@hidden
Hi Saravanan,
> This problem occurs when I unwind from a signal handler, the unwind
> misses the last frame. I have a signal handler for SIGSEGV and this signal
> handler will unwind and print the call sequence.
Last time I checked (which has been a couple of months), GCC did not
emit complete DWARF unwind info which effectively makes it impossible
to reliably unwind from a signal handler. On IA64 this works because
it doesn't use DWARF unwind info.
I filed a bug-report for this a while ago:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18749
Even though the report is for x86-64, it affects all platforms which
use DWARF unwind-info (i.e., pretty much everything but ia64).
--david
--
Mosberger Consulting LLC, voice/fax: 510-744-9372,
http://www.mosberger-consulting.com/
35706 Runckel Lane, Fremont, CA 94536
--
Mosberger Consulting LLC, voice/fax: 510-744-9372,
http://www.mosberger-consulting.com/
35706 Runckel Lane, Fremont, CA 94536
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [libunwind] Fwd: libunwind issue on x86,
David Mosberger-Tang <=