libunwind-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Arun Sharma
Subject: Re: [Libunwind-devel] Re: Backtrace from signal handler on arm from threads
Date: Wed, 2 Feb 2011 07:45:22 -0800

On Wed, Feb 2, 2011 at 1:19 AM, Henrik Grindal Bakken <address@hidden> wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x4026da98 in __errno_location () from /lib/libc.so.6
>
> (gdb) bt
> #0  0x4026da98 in __errno_location () from /lib/libc.so.6
> #1  0x40294d0c in vfprintf () from /lib/libc.so.6
> #2  0x40299284 in ?? () from /lib/libc.so.6
> #3  0x40299284 in ?? () from /lib/libc.so.6

gdb is not able to unwind probably for the same reason why libunwind
is not able to. Where did this libc.so.6 come from? You might have to
use readelf -wf to figure out if there is missing unwind info around
0x40299284.

>
>    [and it goes on forever]
>
>
> Has anyone else had any luck using libunwind with multithreaded arm
> applications?
>

Works just fine on x86.

 -Arun



reply via email to

[Prev in Thread] Current Thread [Next in Thread]