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

[Henrik Grindal Bakken]

Henrik Grindal Bakken <address@hidden>
writes:

> Henrik Grindal Bakken <address@hidden>
> writes:
>
>> Output here:
>> http://fpaste.org/4jfm/
>
> Hmm.  Looking at it, it might seem like libpthread is lacking some
> symbols, creating problems.
>
> One thing, though:  For release software, we'd prefer to ship without
> debugging symbols.  I can accept that that means we have worse
> backtraces, but it's not particularly handy that the unwinding
> segfaults.  Is this hard to avoid?

Copying over a libpthread with more symbols got even further.

Output without UNW_DEBUG_LEVEL: http://fpaste.org/c4yW/
Output with UNW_DEBUG_LEVEL: http://folk.uio.no/hgb/outp2.1.gz

Note the new assertion that goes off.

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