On 17.05.2021 20:27, Alex Bennée wrote:
Luis Machado writes:
Hi,
On 5/14/21 1:06 PM, Alex Bennée wrote:
Hi,
I've been playing around with QEMU's reverse debugging support which
I have working with Pavel's latest patches for supporting virtio with
record/replay. Once you get the right
On Mon, 17 May 2021 at 18:37, Alex Bennée wrote:
> Luis Machado writes:
> > Right. We don't support reverse step/next/continue for remote targets.
> > I think this would be the most appropriate way to implement this
> > feature in GDB. But it is not trivial.
>
> You do because
On 5/17/21 2:27 PM, Alex Bennée wrote:
Luis Machado writes:
Hi,
On 5/14/21 1:06 PM, Alex Bennée wrote:
Hi,
I've been playing around with QEMU's reverse debugging support which
I have working with Pavel's latest patches for supporting virtio with
record/replay. Once you get the right
Luis Machado writes:
> Hi,
>
> On 5/14/21 1:06 PM, Alex Bennée wrote:
>> Hi,
>> I've been playing around with QEMU's reverse debugging support which
>> I have working with Pavel's latest patches for supporting virtio with
>> record/replay. Once you get the right command line it works well
Hi,
On 5/14/21 1:06 PM, Alex Bennée wrote:
Hi,
I've been playing around with QEMU's reverse debugging support which
I have working with Pavel's latest patches for supporting virtio with
record/replay. Once you get the right command line it works well enough
although currently each step
On 14.05.2021 19:06, Alex Bennée wrote:
Hi,
I've been playing around with QEMU's reverse debugging support which
I have working with Pavel's latest patches for supporting virtio with
record/replay. Once you get the right command line it works well enough
although currently each step backwards
Hi,
I've been playing around with QEMU's reverse debugging support which
I have working with Pavel's latest patches for supporting virtio with
record/replay. Once you get the right command line it works well enough
although currently each step backwards requires replaying the entire
execution
