From: Kevin Buettner <kevinb@redhat.com>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC/PATCH] Testsuite: set sysroot when using gdbserver
Date: Thu, 28 Mar 2019 05:14:00 -0000 [thread overview]
Message-ID: <20190327221438.1fade1ef@f29-4.lan> (raw)
In-Reply-To: <20190327134915.5e9b19ba@f29-4.lan>
Hi Alan,
I want to apologize in case my latter comment came across as harsh. I
think I could have phrased it more diplomatically.
I'll note that I also have an interest in setting up sysroot for the
OpenMP tests that I've been working on. So I am genuinely interested
in whether or how sysroot can be set from a board file.
Also, making the tests run faster is definitely a good thing, so
thanks for looking into this.
Kevin
On Wed, 27 Mar 2019 13:49:15 -0700
Kevin Buettner <kevinb@redhat.com> wrote:
> On Wed, 27 Mar 2019 16:40:30 +0000
> Alan Hayward <Alan.Hayward@arm.com> wrote:
>
> > However, I'm not sure if putting the sysroot into gdbserver_start will break
> > other remote setups. In addition, I don't think gdb_test is the correct
> > function to call within the library - for the mi tests this causes a timeout
> > as it expect to use mi_gdb_test.
>
> Can sysroot be set in the board file(s)?
>
> If so, I think that would be preferable to your proposed patch.
>
> Kevin
next prev parent reply other threads:[~2019-03-28 5:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190327164025.48105-1-alan.hayward@arm.com>
2019-03-27 20:49 ` Kevin Buettner
2019-03-28 5:14 ` Kevin Buettner [this message]
2019-03-28 11:02 ` Alan Hayward
[not found] ` <dc692738-2f2b-2995-5a37-a813636d906d@redhat.com>
2019-03-28 12:50 ` Alan Hayward
2019-03-28 14:03 ` Pedro Alves
2019-04-12 20:08 ` Regression on gdb.base/break-probes.exp - native-{,extended-}gdbserver (was: Re: [RFC/PATCH] Testsuite: set sysroot when using gdbserver) Sergio Durigan Junior
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=20190327221438.1fade1ef@f29-4.lan \
--to=kevinb@redhat.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@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