From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gustavo Romero <gustavo.romero@linaro.org>
Cc: qemu-devel@nongnu.org, alex.bennee@linaro.org, thuth@redhat.com,
qemu-arm@nongnu.org
Subject: Re: [PATCH v5 3/9] tests/functional: Provide GDB to the functional tests
Date: Thu, 2 Oct 2025 14:08:18 +0100 [thread overview]
Message-ID: <aN55Qhfia3Sa9Da6@redhat.com> (raw)
In-Reply-To: <20251002020432.54443-4-gustavo.romero@linaro.org>
On Thu, Oct 02, 2025 at 02:04:26AM +0000, Gustavo Romero wrote:
> The probe of GDB is done in 'configure' and the full path is passed to
> meson.build via the -Dgdb=option.
>
> Meson then can pass the location of GDB to the functional tests via an
> environment variable: QEMU_TEST_GDB.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Gustavo Romero <gustavo.romero@linaro.org>
> Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> configure | 2 ++
> meson_options.txt | 2 ++
> scripts/meson-buildoptions.sh | 2 ++
> tests/functional/meson.build | 6 ++++++
> 4 files changed, 12 insertions(+)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-10-02 13:10 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é [this message]
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
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=aN55Qhfia3Sa9Da6@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=gustavo.romero@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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 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).