RE: [libunwind] Unwind information caching for x86-64

[rajagopal, dwarak]

Great work! Now that libunwind should work well for static unwinding in
x86_64, I'm eager to know on how it works for dynamic unwinding. It
right now fails for Ltest-dyn1 and Gtest-dyn1. 
It fails - "FAILURE: expected 13, not 4 frames below signal frame". I
couldn't find code for dynamic unwinding in x86_64 source dir. Is that
still to be implemented or am I missing something? (I do see registering
canceling in mi/ dir) If yes, can anybody give me clues on what part is
to be implemented still?

Thanks,
- Dwarak


-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of David
Mosberger-Tang
Sent: Thursday, February 16, 2006 2:25 PM
To: Nathan Froyd
Cc: Arun Sharma; address@hidden; address@hidden
Subject: Re: [libunwind] Unwind information caching for x86-64

Nathan,

On 2/16/06, Nathan Froyd <address@hidden> wrote:

> On a related note, people who are interested in using libunwind on
> DWARF platforms may be interested in a patch that we recently sent to
> GCC to enable DWARF2 unwind information generation for procedure
> epilogues.

That is encouraging news!  There is a bugzilla post regarding this
which has been pending for at least one year.  Would be nice if GCC
could finally handly this correctly!

  --david
--
Mosberger Consulting LLC, http://www.mosberger-consulting.com/

_______________________________________________
libunwind mailing list
address@hidden
http://www.hpl.hp.com/hosted/linux/mail-archives/libunwind/