[Top][All Lists]

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

Re: [Libunwind-devel] SIGSEGV in ARM+Alarm handler

From: Arun Sharma
Subject: Re: [Libunwind-devel] SIGSEGV in ARM+Alarm handler
Date: Sat, 10 Oct 2015 11:00:01 -0700

On Thu, Oct 8, 2015 at 3:40 AM, Harald Servat <address@hidden> wrote:
> Hello,
>   according to the same core and listing in gdb, the instr value is set by
> dwarf_get which does not returns an error.
>   So can anyone experienced with ARM give his or her thoughts?

I'm not experienced with ARM. But here's what I'd do:

Run with UNW_DEBUG_LEVEL=n (list archives have more info) and get a
trace that shows why dwarf_step() failed.

Recognizing signal frames using instruction signature matching such
as: 0xE92DD800 is fragile and error prone. If the libc you're using
has the right CFI annotation around the signal handler ('S' character
in the CIE augmentation), you'll probably end up with more reliable
stack unwinding.


reply via email to

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