[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Libunwind-devel] Re: Backtrace from signal handler on arm from threads
From: |
Henrik Grindal Bakken |
Subject: |
[Libunwind-devel] Re: Backtrace from signal handler on arm from threads |
Date: |
Tue, 01 Feb 2011 15:32:28 +0100 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) |
Henrik Grindal Bakken <address@hidden>
writes:
> Hello. I'm using (trying to use) libunwind to obtain backtraces for
> my product. The application is running on arm, and is multi-threaded
> (pthreads).
>
> What I see is that the obtain_backtrace() call SIGSEGVs right at the
> beginning when the handler was called from a thread. If it's called
> from the main thread, it doesn't seem to matter that other threads
> exist.
>
> I've tried printf()s immediately in obtain_backtrace(), and if they
> print out the context pointer, they seem to die. The threads are
> created joinable with custom stacks, but changing that doesn't seem to
> affect libunwind.
>
> I compile my product with -g -fno-omit-frame-pointer -mapcs-frame, and
> I've been trying both with 0.99 and latest-and-greatest from git.
The exact same program works as intended on x86, by the way.
--
Henrik Grindal Bakken <address@hidden>
PGP ID: 8D436E52
Fingerprint: 131D 9590 F0CF 47EF 7963 02AF 9236 D25A 8D43 6E52