public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Konstantin Vladimirov <konstantin.vladimirov@gmail.com>
To: gdb@sourceware.org
Subject: Running testsuite on QEMU (sorry if possible duplicate)
Date: Thu, 22 Sep 2022 13:31:21 +0300	[thread overview]
Message-ID: <CADn89gTrG68phJOqvad4nhfM9JRS4XKG9yv8TF=P1EMx=PO-CQ@mail.gmail.com> (raw)

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.

---
With best regards, Konstantin

             reply	other threads:[~2022-09-22 10:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 10:31 Konstantin Vladimirov [this message]
2022-09-23 14:51 ` Simon Marchi
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='CADn89gTrG68phJOqvad4nhfM9JRS4XKG9yv8TF=P1EMx=PO-CQ@mail.gmail.com' \
    --to=konstantin.vladimirov@gmail.com \
    --cc=gdb@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).