On 10/6/20 9:55 PM, Philippe Mathieu-Daudé wrote:
> On 10/3/20 7:14 PM, Pavel Dovgalyuk wrote:
>> From: Pavel Dovgalyuk
>>
>> This is a test for GDB reverse debugging commands: reverse step and reverse
>> continue.
>> Every test in this suite consists of two phases: record and replay.
>> Recordin
On 10/3/20 7:14 PM, Pavel Dovgalyuk wrote:
> From: Pavel Dovgalyuk
>
> This is a test for GDB reverse debugging commands: reverse step and reverse
> continue.
> Every test in this suite consists of two phases: record and replay.
> Recording saves the execution of some instructions and makes an i
On Tue, Oct 06, 2020 at 06:09:55PM +0300, Pavel Dovgalyuk wrote:
> On 06.10.2020 16:36, Cleber Rosa wrote:
> > On Sat, Oct 03, 2020 at 08:14:06PM +0300, Pavel Dovgalyuk wrote:
> > > From: Pavel Dovgalyuk
> > >
> > > This is a test for GDB reverse debugging commands: reverse step and
> > > revers
On 06.10.2020 16:36, Cleber Rosa wrote:
On Sat, Oct 03, 2020 at 08:14:06PM +0300, Pavel Dovgalyuk wrote:
From: Pavel Dovgalyuk
This is a test for GDB reverse debugging commands: reverse step and reverse
continue.
Every test in this suite consists of two phases: record and replay.
Recording sa
On Sat, Oct 03, 2020 at 08:14:06PM +0300, Pavel Dovgalyuk wrote:
> From: Pavel Dovgalyuk
>
> This is a test for GDB reverse debugging commands: reverse step and reverse
> continue.
> Every test in this suite consists of two phases: record and replay.
> Recording saves the execution of some instr
From: Pavel Dovgalyuk
This is a test for GDB reverse debugging commands: reverse step and reverse
continue.
Every test in this suite consists of two phases: record and replay.
Recording saves the execution of some instructions and makes an initial
VM snapshot to allow reverse execution.
Replay s
