Andrey Drobyshev <[email protected]> writes: > A bunch of fixes for functional bugs, cosmetic improvements and fixes > for annoying failures and corner cases which I encounter when using this > script in gdb sessions. Most of them are basically fixups for my previous > commit 42f3c143c3a0 ("scripts/qemugdb: coroutine: Add option for obtaining > detailed trace in coredump"). Still I did split them up cause it'd be a > mess putting them all together. > > Andrey Drobyshev (9): > scripts/qemugdb: coroutine: Fix selected frame leak on error path > scripts/qemugdb: coroutine: Get rid of fallback pattern when dumping > backtrace > scripts/qemugdb: coroutine: Only attempt to restore regs in coredump > scripts/qemugdb: coroutine: Don't unwind past the outermost frame > scripts/qemugdb: coroutine: Fix patching pt_regs in the coredump > scripts/qemugdb: coroutine: Fix '--detailed' description > scripts/qemugdb: coroutine: Handle target absence gracefully > scripts/qemugdb: coroutine: Speed up coroutine lookup in a coredump > scripts/qemugdb: coroutine: Don't touch the coredump for a plain > backtrace > > scripts/qemugdb/coroutine.py | 135 ++++++++++++++++++++++------------- > 1 file changed, 86 insertions(+), 49 deletions(-)
I used this series for debugging both a live process and a coredump. It didn't show any regressions. I can confirm that the exception fixed by patch 4 no longer happens. Tested-by: Fabiano Rosas <[email protected]>
