Re: [Qemu-devel] [PATCH v12 00/25] Fixing record/replay and adding reverse debugging

2019-02-17 Thread Pavel Dovgalyuk
> From: Markus Armbruster [mailto:arm...@redhat.com] > dovgaluk writes: > > > Markus Armbruster писал 2019-02-12 10:14: > >> "Pavel Dovgalyuk" writes: > >> > >>> Ping? > >> > >> Are you pinging for more review, or for someone to merge this? > > > > From my point of view this patch set is ready.

Re: [Qemu-devel] [PATCH v12 00/25] Fixing record/replay and adding reverse debugging

2019-02-12 Thread Markus Armbruster
dovgaluk writes: > Markus Armbruster писал 2019-02-12 10:14: >> "Pavel Dovgalyuk" writes: >> >>> Ping? >> >> Are you pinging for more review, or for someone to merge this? > > From my point of view this patch set is ready. MAINTAINERS Record/replay M: Pavel Dovgalyuk R: Paolo Bonz

Re: [Qemu-devel] [PATCH v12 00/25] Fixing record/replay and adding reverse debugging

2019-02-11 Thread Markus Armbruster
"Pavel Dovgalyuk" writes: > Ping? Are you pinging for more review, or for someone to merge this?

Re: [Qemu-devel] [PATCH v12 00/25] Fixing record/replay and adding reverse debugging

2019-02-11 Thread dovgaluk
Markus Armbruster писал 2019-02-12 10:14: "Pavel Dovgalyuk" writes: Ping? Are you pinging for more review, or for someone to merge this? From my point of view this patch set is ready. Pavel Dovgalyuk

Re: [Qemu-devel] [PATCH v12 00/25] Fixing record/replay and adding reverse debugging

2019-02-11 Thread Pavel Dovgalyuk
Ping? Pavel Dovgalyuk > -Original Message- > From: Pavel Dovgalyuk [mailto:pavel.dovga...@ispras.ru] > Sent: Tuesday, February 05, 2019 11:20 AM > To: qemu-devel@nongnu.org > Cc: kw...@redhat.com; peter.mayd...@linaro.org; war2jor...@live.com; > crosthwaite.pe...@gmail.com; boost.li...@

[Qemu-devel] [PATCH v12 00/25] Fixing record/replay and adding reverse debugging

2019-02-05 Thread Pavel Dovgalyuk
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.