[ Resending from an email address subscribed to the list. Please ignore duplicates ]
On Tue, Apr 27, 2010 at 2:03 AM, Lassi Tuura <[email protected]> wrote: > The good news is that the failures are fixed by the frame-chain walk patch: > > http://thread.gmane.org/gmane.comp.lib.unwind.devel/633 Actually, I get failures even after applying this patch. Ironically, I traced them to the lack of unwind info in src/x86_64/getcontext.S (gdb) bt #0 do_backtrace (may_print=1, get_proc_name=1) at test-async-sig.c:113 #1 0x0000000000400f01 in sighandler (signal=<value optimized out>) at test-async-sig.c:136 #2 <signal handler called> #3 _Ux86_64_getcontext () at x86_64/getcontext.S:65 #4 0x0000000000400c5f in do_backtrace (may_print=0, get_proc_name=0) at test-async-sig.c:80 #5 0x00000000004010bf in main (argc=<value optimized out>, argv=<value optimized out>) at test-async-sig.c:182 Your changes are merely exposing an existing bug, not causing them. -Arun
_______________________________________________ Libunwind-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/libunwind-devel
