[Top][All Lists]

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

Re: [Libunwind-devel] use_prev_instr breaking unwind - how to stop it?

From: Dave Watson
Subject: Re: [Libunwind-devel] use_prev_instr breaking unwind - how to stop it?
Date: Mon, 27 Mar 2017 09:17:17 -0700
User-agent: Mutt/1.6.0 (2016-04-01)

On 03/27/17 08:46 AM, Dave Watson wrote:
> It seems like we would need to parse the unwind info for the current
> frame to correctly fill in use_prev_instr.  It looks like you might be
> able to force this to happen by calling unw_get_proc_info(&c, &pip):
> in Gparser.c:fetch_proc_info will fill in use_prev_instr for the
> cursor. Does that work for you?

> fetch_proc_info checks c->use_prev_instr and, if it is set, decrements the ip
> value as its first action.  Later, it might update c->use_prev_instr, but for
> the first call, I'm stuck with the initial value, as set by unw_init_local.

Ack sorry, nevermind.  Yea I can't think of any way around this
without a new init function, or a heursitic to try use_prev_instr=0 if
we don't find unwind info (or something based on sigreturn maybe).

reply via email to

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