This is the mail archive of the
mailing list for the GDB project.
Re: Unwinding through multiple stacks
- From: Andy Wingo <wingo at igalia dot com>
- To: Doug Evans <dje at google dot com>
- Cc: Alexander Smundak <asmundak at google dot com>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Wed, 25 Mar 2015 08:35:41 +0100
- Subject: Re: Unwinding through multiple stacks
- Authentication-results: sourceware.org; auth=none
- References: <CADPb22ROU+XoYhNhRqLWJycC43nuk9m15GEE3o7f_y_Oie8EzQ at mail dot gmail dot com>
On Wed 25 Mar 2015 01:00, Doug Evans <firstname.lastname@example.org> writes:
> A topic came up on #gdb that the current patches don't cover.
> What if the frame we're trying to unwind through has a different
I was wondering about this too. IIUC this check from GDB isn't a
fundamental limitation -- it's just a convenience for the user, that we
don't keep trying to compute outer frames for what looks to be a corrupt
In these cases I would have the unwinder mark the frame as not needing
an UNWIND_INNER_ID check. Having the check by default is still useful
IMO. How about
(unwind-info-set-discontiguous! unwind-info #t)
or something. That would eventually cause the frame_id to have a
"discontiguous" bitfield marked as 1.
To me it seems appropriate for a followup patch. WDYT?