From: Stefan Hajnoczi <stefanha@redhat.com>
To: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, peterx@redhat.com,
vsementsov@yandex-team.ru, den@virtuozzo.com
Subject: Re: [PATCH v3 0/4] Fixes and improvements for scripts/qemugdb commands
Date: Tue, 6 Jan 2026 13:25:37 -0500 [thread overview]
Message-ID: <20260106182537.GA123256@fedora> (raw)
In-Reply-To: <20251204105019.455060-1-andrey.drobyshev@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]
On Thu, Dec 04, 2025 at 12:50:15PM +0200, Andrey Drobyshev wrote:
> v2 -> v3:
>
> * Use atexit.register() instead of gdb.events.exited.connect() for
> registering a cleanup callback. That way it's called upon both
> normal and abnormal exit;
> * Wrap code in invoke() methods in try-finally block, so that
> restore_regs() is called unconditionally even we caught an exception;
> * Restore registers in cleanup;
> * Set dirty flag early on in patch_regs() to make sure registers get
> restored if we failed while patching.
>
> v1 -> v2:
>
> * Use pty module instead of script(1) for producing colored output;
> * Patch coredump file in place instead of full copy;
> * Save and restore original pt_regs values in a separate file;
> * Wrap this logic in a separate class.
>
> v2: https://lore.kernel.org/qemu-devel/20251202163119.363969-1-andrey.drobyshev@virtuozzo.com/
> v1: https://lore.kernel.org/qemu-devel/20251125142105.448289-1-andrey.drobyshev@virtuozzo.com/
>
> Andrey Drobyshev (4):
> scripts/qemugdb: mtree: Fix OverflowError in mtree with 128-bit
> addresses
> scripts/qemugdb: timers: Fix KeyError in 'qemu timers' command
> scripts/qemugdb: timers: Improve 'qemu timers' command readability
> scripts/qemugdb: coroutine: Add option for obtaining detailed trace in
> coredump
>
> scripts/qemugdb/coroutine.py | 257 +++++++++++++++++++++++++++++++++--
> scripts/qemugdb/mtree.py | 2 +-
> scripts/qemugdb/timers.py | 54 ++++++--
> 3 files changed, 289 insertions(+), 24 deletions(-)
>
> --
> 2.43.5
>
Thanks, applied to my block tree:
https://gitlab.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-01-06 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 10:50 [PATCH v3 0/4] Fixes and improvements for scripts/qemugdb commands Andrey Drobyshev
2025-12-04 10:50 ` [PATCH v3 1/4] scripts/qemugdb: mtree: Fix OverflowError in mtree with 128-bit addresses Andrey Drobyshev
2025-12-04 10:50 ` [PATCH v3 2/4] scripts/qemugdb: timers: Fix KeyError in 'qemu timers' command Andrey Drobyshev
2025-12-04 10:50 ` [PATCH v3 3/4] scripts/qemugdb: timers: Improve 'qemu timers' command readability Andrey Drobyshev
2025-12-04 10:50 ` [PATCH v3 4/4] scripts/qemugdb: coroutine: Add option for obtaining detailed trace in coredump Andrey Drobyshev
2025-12-29 9:05 ` [PATCH v3 0/4] Fixes and improvements for scripts/qemugdb commands Andrey Drobyshev
2026-01-06 18:25 ` Stefan Hajnoczi [this message]
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=20260106182537.GA123256@fedora \
--to=stefanha@redhat.com \
--cc=andrey.drobyshev@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
/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.