From: Simon Marchi <simark@simark.ca>
To: Konstantin Vladimirov <konstantin.vladimirov@gmail.com>,
gdb@sourceware.org
Subject: Re: Running testsuite on QEMU (sorry if possible duplicate)
Date: Fri, 23 Sep 2022 10:51:47 -0400 [thread overview]
Message-ID: <86aeaf80-204b-78dc-89b4-f1745bb75754@simark.ca> (raw)
In-Reply-To: <CADn89gTrG68phJOqvad4nhfM9JRS4XKG9yv8TF=P1EMx=PO-CQ@mail.gmail.com>
On 2022-09-22 06:31, Konstantin Vladimirov via Gdb wrote:
> Hi,
>
> My colleague Ivan already sent this question to this mailing list, but
> it looks like his email hasn't landed.
>
> We are trying to run dejagnu/gdb testsuite on QEMU (RISCV) on Linux.
> Some tests that pass on the local machine fail as they expect having
> shared libs or other binary files at hardcoded paths on a machine
> (QEMU in our case) where the binary is running.
>
> Question is: is it ok to patch gdb testsuite to get rid of hardcoded
> paths. Or maybe this is something intentional?
>
> Example: gdb.base/print-file-var.exp, see SHLIB_NAME variable.
Can you clarify what is your setup?
Are you using a remote host test setup? This would mean that you
cross-compile and "make check" on your host (e.g. your x86-64 machine),
but the testsuite uploads the gdb binary in the VM and runs it there.
And GDB itself would debug the local system natively (in the VM).
Or, are you using a remote target test setup, where the testsuite starts
a gdbserver in the VM and GDB runs on the (e.g. x86-64) host?
Either way, it sounds like that test you mention would be broken either
way, as SHLIB_NAME would be a path on the host. This would be a
mistake, it would need to be fixed. Not many people are using remote
host/target test setups, so these mistakes tend to creep in a lot.
Simon
next prev parent reply other threads:[~2022-09-23 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 10:31 Konstantin Vladimirov
2022-09-23 14:51 ` Simon Marchi [this message]
2022-09-23 15:26 ` Konstantin Vladimirov
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=86aeaf80-204b-78dc-89b4-f1745bb75754@simark.ca \
--to=simark@simark.ca \
--cc=gdb@sourceware.org \
--cc=konstantin.vladimirov@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).