From: Thomas Huth <thuth@redhat.com>
To: Gustavo Romero <gustavo.romero@linaro.org>,
qemu-devel@nongnu.org, alex.bennee@linaro.org,
berrange@redhat.com
Cc: qemu-arm@nongnu.org
Subject: Re: [PATCH v5 0/9] tests/functional: Adapt reverse_debugging to run w/o Avocado
Date: Mon, 6 Oct 2025 09:24:57 +0200 [thread overview]
Message-ID: <b5b739a9-28ef-4d0c-b82b-878e9aee103c@redhat.com> (raw)
In-Reply-To: <30fec60e-b0e8-408c-b577-e4875d8bb133@linaro.org>
Hi Gustavo!
On 03/10/2025 17.07, Gustavo Romero wrote:
> Hi Thomas,
>
> On 10/3/25 11:38, Gustavo Romero wrote:
>> Hi Thomas,
>>
>> On 10/3/25 10:30, Gustavo Romero wrote:
>>> Hi Thomas,
>>>
>>> On 10/2/25 14:52, Thomas Huth wrote:
>>>> On 02/10/2025 18.53, Thomas Huth wrote:
>>>>> On 02/10/2025 04.04, Gustavo Romero wrote:
>>>>>> The goal of this series is to remove Avocado as a dependency for running
>>>>>> the reverse_debugging functional test.
>>>>>>
>>>>>> After several rounds of discussions about v1 and v2, and experiments
>>>>>> done by Daniel and Thomas (thanks for all the experiments and comments
>>>>>> so far), I've taken a new approach and moved away from using a runner
>>>>>> for GDB. The changes, I believe, are much simpler now.
>>>>>
>>>>> Hi Gustavo,
>>>>>
>>>>> unfortunately, this still seems to be broken on Fedora. After applying
>>>>> your series, I get:
>>>>>
>>>>> stderr:
>>>>> Traceback (most recent call last):
>>>>> File "/home/thuth/devel/qemu/tests/functional/reverse_debugging.py",
>>>>> line 100, in reverse_debugging
>>>>> self.reverse_debugging_run(vm, port, gdb_arch, last_icount)
>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>> File "/usr/lib64/python3.13/unittest/case.py", line 156, in
>>>>> skip_wrapper
>>>>> raise SkipTest(reason)
>>>>> unittest.case.SkipTest: Missing env var(s): QEMU_TEST_GDB
>>>>
>>>> Looks like it's required to explicitly use the --gdb=... parameter of
>>>> configure to make it work, and it does not work without that paramter?
>>>> Could you please have a look whether it works without --gdb with the
>>>> auto-detected gdb for you?
...
> I've just tried it on Fedora 42 and GDB is correctly detected:
>
> $ ../configure --target-list=aarch64-softmmu --disable-docs
> $ make -j check-functional-aarch64
I just tried it again, and it just seems to be broken in my build folder
where I do incremental builds. It works when I build QEMU in a new folder
from scratch - quite weird.
> I have installed:
>
> gromero@gromero13:~/git/qemu/build$ dnf info gdb
> Updating and loading repositories:
> Repositories loaded.
> Installed packages
> Name : gdb
> Epoch : 0
> Version : 16.3
> Release : 1.fc42
> Architecture : x86_64
> Installed size : 455.3 KiB
> Source : gdb-16.3-1.fc42.src.rpm
I've got the very same package installed here.
>> Are you sure GDB is installed in your test env?
>>
>> Do mind checking if:
>>
>> gromero@gromero0:/mnt/git/qemu_$ gdb_bin=$(command -v "gdb-multiarch" ||
>> command -v "gdb")
>> gromero@gromero0:/mnt/git/qemu_$ echo $gdb_bin
>> /usr/bin/gdb
>>
>> works in your env and if QEMU_TEST_GDB is in:
>>
>> $ ./pyvenv/bin/meson test --verbose --no-rebuild -t 1 --setup thorough
>> --suite func-thorough func-aarch64-reverse_debug
>>
>> output?
$ echo $gdb_bin
/usr/bin/gdb
Thomas
next prev parent reply other threads:[~2025-10-06 7:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 2:04 [PATCH v5 0/9] tests/functional: Adapt reverse_debugging to run w/o Avocado Gustavo Romero
2025-10-02 2:04 ` [PATCH v5 1/9] tests/functional: Re-activate the check-venv target Gustavo Romero
2025-10-02 13:06 ` Daniel P. Berrangé
2025-10-02 16:08 ` Thomas Huth
2025-10-02 2:04 ` [PATCH v5 2/9] python: Install pygdbmi in meson's venv Gustavo Romero
2025-10-02 13:06 ` Daniel P. Berrangé
2025-10-14 17:39 ` John Snow
2025-10-14 18:21 ` Thomas Huth
2025-10-14 18:55 ` John Snow
2025-10-14 18:59 ` Thomas Huth
2025-10-14 19:05 ` John Snow
2025-10-14 19:19 ` Thomas Huth
2025-10-02 2:04 ` [PATCH v5 3/9] tests/functional: Provide GDB to the functional tests Gustavo Romero
2025-10-02 13:08 ` Daniel P. Berrangé
2025-10-02 2:04 ` [PATCH v5 4/9] tests/functional: Add GDB class Gustavo Romero
2025-10-02 13:11 ` Daniel P. Berrangé
2025-10-02 16:24 ` Alex Bennée
2025-10-02 2:04 ` [PATCH v5 5/9] tests/functional: replace avocado process with subprocess Gustavo Romero
2025-10-02 2:04 ` [PATCH v5 6/9] tests/functional: drop datadrainer class in reverse debugging Gustavo Romero
2025-10-02 2:04 ` [PATCH v5 7/9] tests/functional: Add decorator to skip test on missing env vars Gustavo Romero
2025-10-02 13:12 ` Daniel P. Berrangé
2025-10-02 2:04 ` [PATCH v5 8/9] tests/functional: Adapt reverse_debugging to run w/o Avocado Gustavo Romero
2025-10-02 13:13 ` Daniel P. Berrangé
2025-10-02 2:04 ` [PATCH v5 9/9] tests/functional: Adapt arches to reverse_debugging " Gustavo Romero
2025-10-02 13:14 ` Daniel P. Berrangé
2025-10-02 16:53 ` [PATCH v5 0/9] tests/functional: Adapt reverse_debugging to run " Thomas Huth
2025-10-02 17:52 ` Thomas Huth
2025-10-03 13:30 ` Gustavo Romero
2025-10-03 14:38 ` Gustavo Romero
2025-10-03 15:07 ` Gustavo Romero
2025-10-06 7:24 ` Thomas Huth [this message]
2025-10-06 9:58 ` Alex Bennée
2025-10-06 10:07 ` Thomas Huth
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=b5b739a9-28ef-4d0c-b82b-878e9aee103c@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=gustavo.romero@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).