[Libunwind-devel] Re: Backtrace from signal handler on arm from threads

[Henrik Grindal Bakken]

Lassi Tuura <address@hidden> writes:

> Hi,
>
>> I've read that thread, and it's very interesting.  I did have the
>> same problems as Sven, but got around that by building glibc with
>> -g and shipping with a non-stripped library (actually, with a
>> stripped library, and a --add-gnu-debuglink to a debug-symbols-only
>> library as well).  Now libunwind works like a charm, except in the
>> case of multi-threaded apps, which mine happens to be...
>
> Right, I just meant if you post the debug output as in that thread,
> then other people can help you diagnose the problems. I know
> relatively little about ARM but I do understand readelf output and
> libunwind debug output and can help with those sorts of issues.

Here we go:

The readelf output is at http://folk.uio.no/hgb/readelf.output.gz

GDB session: http://fpaste.org/jPwF/

It appears to SEGFAULT upon calling sigprocmask().

"UNW_DEBUG_LEVEL=1011 /tmp/backtrace" actually prints nothing.  It
appears to segfault before libunwind manages to output anything at
all.  If I run my program without creating threads, I get lots of
output.  libunwind was built with --enable-debug and
--enable-debug-frame.


-- 
Henrik Grindal Bakken <address@hidden>
PGP ID: 8D436E52
Fingerprint: 131D 9590 F0CF 47EF 7963  02AF 9236 D25A 8D43 6E52