[Libunwind-devel] libunwind on x86-64 w/ C++ exceptions

[Mark Rabkin]

Hi Friendly libunwind Devs,

 

I'm trying to get libunwind working on my builds on x86-64 (AMD ~2GHz chips), on Linux 2.6 with GCC 4.1.  The reason I'm trying to use libunwind, like probably many others, is to try to use the Google Perf Tools (cpu profiler and TCMalloc).

 

I'm getting programs dumping core when throwing C++ exceptions and there's objects w/ destructors on the stack that has to be unrolled -- the core dump winds up in ""__gxx_ personality_v0" under "_Unwind_Resume".   I'll provide a small example w/ a stack trace soon.

 

Is this kind of behavior still quasi-expected on x86-64, or is libunwind in a state where C++ exceptions should now work on this platform?  I look at the mailing list archives, and there seem to have been some patches for this type of problem.

 

Is there a latest build I can grab from git that might solve this? 

 

I'm using the 2007/10/18 snapshot of libunwind-0.99-alpha.

 

 

- Mark