nu.org/msg560780.html
>
>
>
> Pavel Dovgalyuk
>
>
>
> *From:* Artem Pisarenko [mailto:artem.k.pisare...@gmail.com]
> *Sent:* Tuesday, October 09, 2018 2:24 PM
> *To:* Pavel Dovgalyuk
>
>
> *Cc:* pavel.dovga...@ispras.ru; qemu-devel@nongnu.org
> *Subject:
: Re: [Qemu-devel] [PATCH v6 00/25] Fixing record/replay and adding
reverse debugging
(Since all previous patches are already merged to master, I'm running tests
against latest (almost) version from master branch. Following results are based
on master c
eport("'preconfig' and 'incoming' options are "
>
>
>
> Pavel Dovgalyuk
>
>
>
> *From:* Artem Pisarenko [mailto:artem.k.pisare...@gmail.com]
> *Sent:* Thursday, October 04, 2018 4:16 PM
> *To:* dovgaluk
> *Cc:* pavel.dovga...@ispras.ru
rror_report("'preconfig' and 'incoming' options are "
Pavel Dovgalyuk
From: Artem Pisarenko [mailto:artem.k.pisare...@gmail.com]
Sent: Thursday, October 04, 2018 4:16 PM
To: dovgaluk
Cc: pavel.dovga...@ispras.ru; qemu-devel@nongnu.org
Subject: Re: [Qemu-devel]
No, it didn't changed test results, at least for
https://github.com/ispras/qemu/tree/rr-180911 . Even step values it stucks
on are same for most runs.
Playing with master and my own branch gives different results for tests
without sleep=off and -rtc base. It seems that patch you mentioned didn't
ch
Can you try applying this patch?
https://www.mail-archive.com/qemu-devel@nongnu.org/msg563798.html
I also encountered the problems with x86_64 replaying and found the
misprint in
the code which was fixed later, than sending the series to the mailing
list.
Pavel Dovgalyuk
Artem Pisarenko пис
I've added "-monitor stdio" option to command line of Test 1 and repeated
entering command during execution:
QEMU 3.0.50 monitor - type 'help' for more information
(qemu) info replay
Replaying execution 'icount_rr_capture.bin': current step = 311736195
(qemu) info replay
Replaying execut
I've posted bug report with extended tests (incl. case without sleep=off).
You may find guest image (kernel) in bug description.
https://bugs.launchpad.net/qemu/+bug/1795369
The most annoying thing is that some issues are almost not reproducible.
There are definitely race conditions somewhere in q
Artem Pisarenko писал 2018-09-30 14:01:
Feature still broken :(
Thanks for testing.
Brief description of my tests.
Guest image is Linux, which just powers off after kernel boots
(instead of proceeding to user-space /init or /sbin/init).
Base cmdline:
qemu-system-x86_64 -nodefaults -machine
Feature still broken :(
Brief description of my tests.
Guest image is Linux, which just powers off after kernel boots (instead of
proceeding to user-space /init or /sbin/init).
Base cmdline:
qemu-system-x86_64 -nodefaults -machine pc,accel=tcg -m 2048 -cpu qemu64
-rtc clock=vm,base=2000-01-01T00:
On 13/09/2018 15:40, Pavel Dovgalyuk wrote:
>> For now I'm queuing 12, 14, 19, 20 (pending question to you) and 23-25.
> What about patch 21?
I'd want an ACK from the IDE maintainer. Let's add him to Cc.
Paolo
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> On 12/09/2018 10:17, Pavel Dovgalyuk wrote:
> > 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 t
On 12/09/2018 10:17, Pavel Dovgalyuk wrote:
> 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
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.
14 matches
Mail list logo
