[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH] scripts/qemugdb: support coroutine backtrace in
From: |
Simon Marchi |
Subject: |
Re: [Qemu-devel] [PATCH] scripts/qemugdb: support coroutine backtrace in coredumps |
Date: |
Sun, 22 Apr 2018 21:37:52 -0400 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
On 2018-04-09 10:08 PM, Stefan Hajnoczi wrote:
> I wonder what the point of select-frame is then...
>
> I have CCed the GDB mailing list. Maybe someone can help us. Context:
>
> QEMU implements coroutines using jmpbuf. We'd like to print coroutine
> call stacks in GDB and have a script that works when a process is being
> debugged (it sets the registers).
>
> Now we'd like to extend the script to work on core dumps where it's not
> possible to set registers (since there is no process being debugged).
>
> Is there a way to backtrace an arbitrary call stack in a core dump?
Not that I know of. The "frame <stack-addr> <pc-addr>" form of the frame
command sounds like it should be usable to achieve that, but it doesn't
seem to work in that way. I really wonder if it's working as it was
intended initially. I guess using that form of the frame command should
override/mask the real current values of $sp and $pc?
Simon