qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, wrampazz@redhat.com, pavel.dovgalyuk@ispras.ru,
	ehabkost@redhat.com, alex.bennee@linaro.org, mtosatti@redhat.com,
	armbru@redhat.com, mreitz@redhat.com, stefanha@redhat.com,
	crosa@redhat.com, pbonzini@redhat.com, philmd@redhat.com,
	zhiwei_liu@c-sky.com, rth@twiddle.net
Subject: [PATCH 00/13] Reverse debugging
Date: Fri, 26 Jun 2020 13:19:40 +0300	[thread overview]
Message-ID: <159316678008.10508.6615172353109944370.stgit@pasha-ThinkPad-X280> (raw)

GDB remote protocol supports reverse debugging of the targets.
It includes 'reverse step' and 'reverse continue' operations.
The first one finds the previous step of the execution,
and the second one is intended to stop at the last breakpoint that
would happen when the program is executed normally.

Reverse debugging is possible in the replay mode, when at least
one snapshot was created at the record or replay phase.
QEMU can use these snapshots for travelling back in time with GDB.

Running the execution in replay mode allows using GDB reverse debugging
commands:
 - reverse-stepi (or rsi): Steps one instruction to the past.
   QEMU loads on of the prior snapshots and proceeds to the desired
   instruction forward. When that step is reaches, execution stops.
 - reverse-continue (or rc): Runs execution "backwards".
   QEMU tries to find breakpoint or watchpoint by loaded prior snapshot
   and replaying the execution. Then QEMU loads snapshots again and
   replays to the latest breakpoint. When there are no breakpoints in
   the examined section of the execution, QEMU finds one more snapshot
   and tries again. After the first snapshot is processed, execution
   stops at this snapshot.

The set of patches include the following modifications:
 - gdbstub update for reverse debugging support
 - functions that automatically perform reverse step and reverse
   continue operations
 - hmp/qmp commands for manipulating the replay process
 - improvement of the snapshotting for saving the execution step
   in the snapshot parameters
 - avocado-based acceptance tests for reverse debugging

Acceptance tests intended to use the version of avocado framework, that
will be released after 25.06.20, because it includes significant
fixes of the remote GDB protocol.

The patches are available in the repository:
https://github.com/ispras/qemu/tree/rr-200626

---

Pavel Dovgaluk (13):
      replay: provide an accessor for rr filename
      qcow2: introduce icount field for snapshots
      migration: introduce icount field for snapshots
      iotests: update snapshot test for new output format
      qapi: introduce replay.json for record/replay-related stuff
      replay: introduce info hmp/qmp command
      replay: introduce breakpoint at the specified step
      replay: implement replay-seek command
      replay: flush rr queue before loading the vmstate
      gdbstub: add reverse step support in replay mode
      gdbstub: add reverse continue support in replay mode
      replay: describe reverse debugging in docs/replay.txt
      tests/acceptance: add reverse debugging test


 0 files changed

--
Pavel Dovgalyuk


             reply	other threads:[~2020-06-26 13:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 10:19 Pavel Dovgalyuk [this message]
2020-06-26 10:19 ` [PATCH 01/13] replay: provide an accessor for rr filename Pavel Dovgalyuk
2020-06-26 10:19 ` [PATCH 02/13] qcow2: introduce icount field for snapshots Pavel Dovgalyuk
2020-07-06 20:17   ` Eric Blake
2020-07-16  6:43     ` Pavel Dovgalyuk
2020-06-26 10:19 ` [PATCH 03/13] migration: " Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 04/13] iotests: update snapshot test for new output format Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 05/13] qapi: introduce replay.json for record/replay-related stuff Pavel Dovgalyuk
2020-07-15 11:20   ` Alex Bennée
2020-07-16  6:00     ` Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 06/13] replay: introduce info hmp/qmp command Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 07/13] replay: introduce breakpoint at the specified step Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 08/13] replay: implement replay-seek command Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 09/13] replay: flush rr queue before loading the vmstate Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 10/13] gdbstub: add reverse step support in replay mode Pavel Dovgalyuk
2020-07-15 11:27   ` Alex Bennée
2020-06-26 10:20 ` [PATCH 11/13] gdbstub: add reverse continue " Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 12/13] replay: describe reverse debugging in docs/replay.txt Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 13/13] tests/acceptance: add reverse debugging test Pavel Dovgalyuk
2020-07-06  6:02 ` [PATCH 00/13] Reverse debugging Pavel Dovgalyuk
2020-07-06 19:55   ` Alex Bennée
2020-07-07  5:00     ` Pavel Dovgalyuk

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=159316678008.10508.6615172353109944370.stgit@pasha-ThinkPad-X280 \
    --to=pavel.dovgalyuk@ispras.ru \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=stefanha@redhat.com \
    --cc=wrampazz@redhat.com \
    --cc=zhiwei_liu@c-sky.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).