aboutsummaryrefslogtreecommitdiff
path: root/scripts/qemu-gdb.py
diff options
context:
space:
mode:
authorMaxim Levitsky <mlevitsk@redhat.com>2020-12-17 17:54:35 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2021-01-12 12:38:03 +0100
commit4cbf8efc5b894f9dd86867d7e3de8e8f190618c4 (patch)
tree51792dae23a6def2523e0614ac49fe51655bb2af /scripts/qemu-gdb.py
parentcb7abd8319d19000b57ae6c5c474c2635db054c6 (diff)
downloadqemu-4cbf8efc5b894f9dd86867d7e3de8e8f190618c4.zip
qemu-4cbf8efc5b894f9dd86867d7e3de8e8f190618c4.tar.gz
qemu-4cbf8efc5b894f9dd86867d7e3de8e8f190618c4.tar.bz2
scripts/gdb: fix 'qemu coroutine' when users selects a non topmost stack frame
The code that dumps the stack frame works like that: * save current registers * overwrite current registers (including rip/rsp) with coroutine snapshot in the jmpbuf * print backtrace * restore the saved registers. If the user has currently selected a non topmost stack frame in gdb, the above code will still restore the selected frame registers, but the gdb will then lose the selected frame index, which makes it impossible to switch back to frame 0, to continue debugging the executable. Therefore switch temporarily to the topmost frame of the stack for the above code. Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com> Message-Id: <20201217155436.927320-2-mlevitsk@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/qemu-gdb.py')
0 files changed, 0 insertions, 0 deletions