I've done more investigation.
It was barfing on the most trivial of any exception throws when I link
"libunwind.a" or "libunwind.so". However, stack unrolling after exceptions
seems to work if I link libunwind-x86_64.{a,so} instead. What's the exact
difference between these two versions of the library? I can't find any docs
that detail it, but I've played around with "nm" and it seems to be a lot of
symbol name changes.
Unfortunately, the google perftools seem to want symbols from libunwind that
aren't present in libunwind-x86_64 (since the names seem to be different, a
lot of changes from UL to U).
Any hints?
- Mark
On 2/15/08 1:30 PM, "Arun Sharma" <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 15, 2008 at 12:27 PM, Mark Rabkin <[EMAIL PROTECTED]> wrote:
>> 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.
>
> This is fixed by:
>
> http://git.kernel.org/gitweb.cgi?p=libs/libunwind/libunwind.git;a=commit;h=314
> 40e9796bb34146372df52ed59c4f68ea5839d
>
> -Arun
>
>
>
_______________________________________________
Libunwind-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/libunwind-devel
