qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v4 00/15] Reverse debugging


From: Philippe Mathieu-Daudé
Subject: Re: [PATCH v4 00/15] Reverse debugging
Date: Mon, 21 Sep 2020 09:20:55 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0

On 9/21/20 8:48 AM, Pavel Dovgalyuk wrote:
> On 20.09.2020 10:58, Paolo Bonzini wrote:
>> On 14/09/20 08:06, 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
>>> 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.
>>
>> I had queued this, it is a very nice patch series.  Unfortunately, the
>> tests failed on gitlab:
>>
>> https://gitlab.com/bonzini/qemu/-/jobs/745795080
> 
> There are other tests that were disabled on gitlab for the unknown reason.
> 
> https://patchwork.kernel.org/patch/11636515/

Unrelated.

> https://patchwork.kernel.org/patch/11701681/
> 
> The latter is related to machine_rx_gdbsim.py

Unrelated, 'gdbsim' is the name of the machine. It is not
using the gdbstub/gdb protocol.

> Could it be the same avocado/python/etc issue with socket interaction?

Yes, likely...

The kludge is to simply add (with an explanation if possible):

  @skipIf(os.getenv('GITLAB_CI'), 'Running on GitLab')

> 
> 
> Pavel Dovgalyuk
> 
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]