From: "Pavel Dovgalyuk" <dovgaluk@ispras.ru>
To: "'Alex Bennée'" <alex.bennee@linaro.org>
Cc: kwolf@redhat.com, peter.maydell@linaro.org,
pavel.dovgaluk@ispras.ru, crosthwaite.peter@gmail.com,
ciro.santilli@gmail.com, jasowang@redhat.com,
quintela@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com,
maria.klimushenkova@ispras.ru, mst@redhat.com, kraxel@redhat.com,
boost.lists@gmail.com, thomas.dullien@googlemail.com,
pbonzini@redhat.com, mreitz@redhat.com,
artem.k.pisarenko@gmail.com, dgilbert@redhat.com,
rth@twiddle.net
Subject: RE: [for-5.0 PATCH 00/11] Support for reverse debugging with GDB
Date: Thu, 16 Jan 2020 14:26:28 +0300 [thread overview]
Message-ID: <000f01d5cc5f$cccb90b0$6662b210$@ru> (raw)
In-Reply-To: <87o8v3lkq8.fsf@linaro.org>
> From: Alex Bennée [mailto:alex.bennee@linaro.org]
> Pavel Dovgalyuk <pavel.dovgaluk@gmail.com> writes:
>
> > 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
> >
> > The patches are available in the repository:
> > https://github.com/ispras/qemu/tree/rr-191223
>
> So I tried with your additional patch. Launching QEMU as:
>
> ./aarch64-softmmu//qemu-system-aarch64 -monitor none \
> -display none -M virt -cpu max -display none \
> -semihosting-config enable=on \
> -kernel ./tests/tcg/aarch64-softmmu/memory \
> -icount shift=5,rr=replay,rrfile=record.bin \
> -s -S -d trace:gdbstub\*
>
> And gdb:
>
> gdb tests/tcg/aarch64-softmmu/memory \
> -ex "target remote localhost:1234"
>
> I get the following log:
>
> (gdb) x/3i $pc
> => 0x400037b0 <__start>: adr x0, 0x40003000 <vector_table>
> 0x400037b4 <__start+4>: msr vbar_el1, x0
> 0x400037b8 <__start+8>: adrp x0, 0x40200000
> (gdb) p/x $x0
> $1 = 0x0
> (gdb) si
> 92 msr vbar_el1, x0
> (gdb) p/x $x0
> $2 = 0x40003000
> (gdb) rsi
> warning: Remote failure reply: E14
>
> Program stopped.
> __start () at /home/alex.bennee/lsrc/qemu.git/tests/tcg/aarch64/system/boot.S:92
> 92 msr vbar_el1, x0
> (gdb) p/x $x0
> $3 = 0x40003000
>
> So it doesn't seem to be working.
That's ok, you'll need at least one VM snapshot available to recover the initial VM state.
Try changing the command lines in the following way:
First, create empty.qcow2 which will be used for saving the snapshots.
Then record with initial snapshot and attached empty.qcow2:
./aarch64-softmmu//qemu-system-aarch64 -monitor none \
-display none -M virt -cpu max \
-kernel ./tests/tcg/aarch64-softmmu/memory \
-icount shift=5,rr=record,rrfile=record.bin,rrsnapshot=init \
-drive file=empty.qcow2
After that you can replay the execution with the support of reverse debugging:
./aarch64-softmmu//qemu-system-aarch64 -monitor none \
-display none -M virt -cpu max \
-kernel ./tests/tcg/aarch64-softmmu/memory \
-icount shift=5,rr=replay,rrfile=record.bin,rrsnapshot=init \
-drive file=empty.qcow2
I removed "-semihosting-config enable=on", because I'm not sure what is it for.
It may break the replay, because there is no implementation of
semihosting input record/replay.
Pavel Dovgalyuk
next prev parent reply other threads:[~2020-01-16 11:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 9:45 [for-5.0 PATCH 00/11] Support for reverse debugging with GDB Pavel Dovgalyuk
2019-12-23 9:46 ` [for-5.0 PATCH 01/11] replay: provide an accessor for rr filename Pavel Dovgalyuk
2019-12-23 9:46 ` [for-5.0 PATCH 02/11] qcow2: introduce icount field for snapshots Pavel Dovgalyuk
2020-01-09 11:48 ` Kevin Wolf
2019-12-23 9:47 ` [for-5.0 PATCH 03/11] migration: " Pavel Dovgalyuk
2020-01-09 11:59 ` Kevin Wolf
2020-01-13 17:11 ` Alex Bennée
2020-01-14 9:32 ` Pavel Dovgalyuk
2019-12-23 9:47 ` [for-5.0 PATCH 04/11] qapi: introduce replay.json for record/replay-related stuff Pavel Dovgalyuk
2019-12-23 9:47 ` [for-5.0 PATCH 05/11] replay: introduce info hmp/qmp command Pavel Dovgalyuk
2020-01-09 12:23 ` Alex Bennée
2020-01-09 12:27 ` Pavel Dovgalyuk
2019-12-23 9:47 ` [for-5.0 PATCH 06/11] replay: introduce breakpoint at the specified step Pavel Dovgalyuk
2019-12-23 9:47 ` [for-5.0 PATCH 07/11] replay: implement replay-seek command Pavel Dovgalyuk
2019-12-23 9:48 ` [for-5.0 PATCH 08/11] replay: flush rr queue before loading the vmstate Pavel Dovgalyuk
2020-01-13 17:48 ` Alex Bennée
2020-01-14 13:57 ` Pavel Dovgalyuk
2019-12-23 9:48 ` [for-5.0 PATCH 09/11] gdbstub: add reverse step support in replay mode Pavel Dovgalyuk
2019-12-23 9:48 ` [for-5.0 PATCH 10/11] gdbstub: add reverse continue " Pavel Dovgalyuk
2019-12-23 9:48 ` [for-5.0 PATCH 11/11] replay: describe reverse debugging in docs/replay.txt Pavel Dovgalyuk
2020-01-09 6:13 ` [for-5.0 PATCH 00/11] Support for reverse debugging with GDB Pavel Dovgalyuk
2020-01-09 12:00 ` Kevin Wolf
2020-01-09 12:12 ` Pavel Dovgalyuk
2020-01-13 9:29 ` Markus Armbruster
2020-01-13 9:35 ` Pavel Dovgalyuk
2020-01-13 10:06 ` Kevin Wolf
2020-01-13 10:14 ` Peter Maydell
2020-01-13 10:27 ` Kevin Wolf
2020-01-13 10:47 ` Peter Maydell
2020-01-13 17:55 ` Alex Bennée
2020-01-16 11:11 ` Alex Bennée
2020-01-16 11:26 ` Pavel Dovgalyuk [this message]
2020-01-17 17:40 ` Alex Bennée
2020-01-20 11:58 ` 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='000f01d5cc5f$cccb90b0$6662b210$@ru' \
--to=dovgaluk@ispras.ru \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=artem.k.pisarenko@gmail.com \
--cc=boost.lists@gmail.com \
--cc=ciro.santilli@gmail.com \
--cc=crosthwaite.peter@gmail.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=maria.klimushenkova@ispras.ru \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
--cc=thomas.dullien@googlemail.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).