From: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: stefanha@redhat.com, kwolf@redhat.com, peterx@redhat.com,
farosas@suse.de
Subject: Re: [PATCH 0/9] scripts/qemugdb: some fixes for 'qemu bt' / 'qemu coroutine' commands
Date: Wed, 23 Sep 2026 18:28:36 +0300 [thread overview]
Message-ID: <28fc03f8-6383-4036-a405-fb3e70f49a6b@virtuozzo.com> (raw)
In-Reply-To: <20260804151743.937694-1-andrey.drobyshev@virtuozzo.com>
On 8/4/26 6:17 PM, Andrey Drobyshev wrote:
> 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(-)
Friendly ping
If someone else is using this tool for debugging - there're some genuine
bug fixes in this series. The bugs were also introduced by me, so
that's more of a cleanup :)
Andrey
next prev parent reply other threads:[~2026-09-23 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 15:17 [PATCH 0/9] scripts/qemugdb: some fixes for 'qemu bt' / 'qemu coroutine' commands Andrey Drobyshev
2026-08-04 15:17 ` [PATCH 1/9] scripts/qemugdb: coroutine: Fix selected frame leak on error path Andrey Drobyshev
2026-08-04 15:17 ` [PATCH 2/9] scripts/qemugdb: coroutine: Get rid of fallback pattern when dumping backtrace Andrey Drobyshev
2026-08-04 15:17 ` [PATCH 3/9] scripts/qemugdb: coroutine: Only attempt to restore regs in coredump Andrey Drobyshev
2026-08-04 15:17 ` [PATCH 4/9] scripts/qemugdb: coroutine: Don't unwind past the outermost frame Andrey Drobyshev
2026-08-04 15:17 ` [PATCH 5/9] scripts/qemugdb: coroutine: Fix patching pt_regs in the coredump Andrey Drobyshev
2026-08-04 15:17 ` [PATCH 6/9] scripts/qemugdb: coroutine: Fix '--detailed' description Andrey Drobyshev
2026-08-04 15:17 ` [PATCH 7/9] scripts/qemugdb: coroutine: Handle target absence gracefully Andrey Drobyshev
2026-08-04 15:17 ` [PATCH 8/9] scripts/qemugdb: coroutine: Speed up coroutine lookup in a coredump Andrey Drobyshev
2026-08-04 15:17 ` [PATCH 9/9] scripts/qemugdb: coroutine: Don't touch the coredump for a plain backtrace Andrey Drobyshev
2026-08-26 15:02 ` [PATCH 0/9] scripts/qemugdb: some fixes for 'qemu bt' / 'qemu coroutine' commands Fabiano Rosas
2026-09-23 15:28 ` Andrey Drobyshev [this message]
2026-09-25 14:03 ` Kevin Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28fc03f8-6383-4036-a405-fb3e70f49a6b@virtuozzo.com \
--to=andrey.drobyshev@virtuozzo.com \
--cc=farosas@suse.de \
--cc=kwolf@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.