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

[Lassi Tuura]

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.

Regards,
Lassi