All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, wrampazz@redhat.com, ehabkost@redhat.com,
	alex.bennee@linaro.org, mtosatti@redhat.com, armbru@redhat.com,
	mreitz@redhat.com, stefanha@redhat.com, crosa@redhat.com,
	philmd@redhat.com, zhiwei_liu@c-sky.com, rth@twiddle.net
Subject: Re: [PATCH v4 00/15] Reverse debugging
Date: Mon, 21 Sep 2020 09:24:24 +0300	[thread overview]
Message-ID: <38bc996d-b7e6-e89e-f166-2623b0ce554e@ispras.ru> (raw)
In-Reply-To: <70d75fb9-fb91-8574-2f69-f730969a61ba@ispras.ru>

On 21.09.2020 09:03, 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 is a strange thing in your environment:
> 
> 15:49:41 INFO | Downloading/preparing boot image
> 15:49:42 INFO | Running '/builds/bonzini/qemu/build/qemu-img create -f 
> qcow2 -b 
> /builds/bonzini/qemu/avocado-cache/by_location/d2a8d6b607afec50de14560c064f34ffd99836b2/Fedora-Cloud-Base-31-1.9.x86_64.qcow2 
> /var/tmp/avocado_tj2janfx/avocado_job_ys7ueohj/04-tests_acceptance_boot_linux.py_BootLinuxX8664.test_pc_q35_kvm/Fedora-Cloud-Base-31-1.9.x86_64-d1ac1224.qcow2' 
> 
> 
> 
> It downloads boot image, but there is no such requirement in the test.
> And all this stuff consumes most of the time for the test.

Sorry, that was ok. It was the output from the previous test.

For reverse debugging there was a timeout on reading from the socket: 
result = self._socket.recv(REMOTE_MAX_PACKET_SIZE)

Do you have any hint how to debug such a failure in this environment?

Pavel Dovgalyuk


  reply	other threads:[~2020-09-21  6:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  6:06 [PATCH v4 00/15] Reverse debugging Pavel Dovgalyuk
2020-09-14  6:06 ` [PATCH v4 01/15] replay: don't record interrupt poll Pavel Dovgalyuk
2020-09-14  6:06 ` [PATCH v4 02/15] replay: provide an accessor for rr filename Pavel Dovgalyuk
2020-09-14  6:06 ` [PATCH v4 03/15] qcow2: introduce icount field for snapshots Pavel Dovgalyuk
2020-09-14  6:06 ` [PATCH v4 04/15] migration: " Pavel Dovgalyuk
2020-09-14  6:06 ` [PATCH v4 05/15] qapi: introduce replay.json for record/replay-related stuff Pavel Dovgalyuk
2020-09-14  6:07 ` [PATCH v4 06/15] replay: introduce info hmp/qmp command Pavel Dovgalyuk
2020-09-14  6:07 ` [PATCH v4 07/15] replay: introduce breakpoint at the specified step Pavel Dovgalyuk
2020-09-14  6:07 ` [PATCH v4 08/15] replay: implement replay-seek command Pavel Dovgalyuk
2020-09-14  6:07 ` [PATCH v4 09/15] replay: flush rr queue before loading the vmstate Pavel Dovgalyuk
2020-09-14  6:07 ` [PATCH v4 10/15] gdbstub: add reverse step support in replay mode Pavel Dovgalyuk
2020-09-14  6:07 ` [PATCH v4 11/15] gdbstub: add reverse continue " Pavel Dovgalyuk
2020-09-14  6:07 ` [PATCH v4 12/15] replay: describe reverse debugging in docs/replay.txt Pavel Dovgalyuk
2020-09-14  6:07 ` [PATCH v4 13/15] docs: convert replay.txt to rst Pavel Dovgalyuk
2020-09-14  6:07 ` [PATCH v4 14/15] replay: create temporary snapshot at debugger connection Pavel Dovgalyuk
2020-09-14  6:07 ` [PATCH v4 15/15] tests/acceptance: add reverse debugging test Pavel Dovgalyuk
2020-09-20  7:58 ` [PATCH v4 00/15] Reverse debugging Paolo Bonzini
2020-09-21  6:03   ` Pavel Dovgalyuk
2020-09-21  6:24     ` Pavel Dovgalyuk [this message]
2020-09-21  6:48   ` Pavel Dovgalyuk
2020-09-21  7:20     ` Philippe Mathieu-Daudé

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38bc996d-b7e6-e89e-f166-2623b0ce554e@ispras.ru \
    --to=pavel.dovgalyuk@ispras.ru \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=stefanha@redhat.com \
    --cc=wrampazz@redhat.com \
    --cc=zhiwei_liu@c-sky.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.