Re: How to backtrace an separate stack?

[Pedro Alves]

On 2022-03-07 16:58, Tom Tromey wrote:
>>>>>> "Stefan" == Stefan Hajnoczi <stefanha@redhat.com> writes:
> 
> Stefan> I hoped that "select-frame address ADDRESS" could be used instead so
> Stefan> this would work on coredumps too. Unfortunately "select-frame" only
> Stefan> searches stack frames that GDB is already aware of, so it cannot be 
> used
> Stefan> to backtrace coroutine stacks.
> 
> I wonder if "select-frame view" is closer to what you want.
> 
> I can't attest to how well it works or doesn't work.  I've never tried
> it.

A backtrace after "select-frame view" will still start at the
current (machine register's) frame.  Maybe it's sufficient to emulate it with
a sequence of "up" + "frame", though.  Keep in mind that you'll lose the view
with "info threads" or any command that flushes the frame cache internally,
as I mentioned in that ancient discussion.