This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Unwinding through multiple stacks


Hi,

On Wed 25 Mar 2015 01:00, Doug Evans <dje@google.com> 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
> stack?

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
stack.

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?

Andy


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]