From: Simon Marchi <simark@simark.ca>
To: Alan Hayward <Alan.Hayward@arm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: nd <nd@arm.com>
Subject: Re: [PATCH] Testsuite: Ensure pie is disabled on some tests
Date: Tue, 19 Mar 2019 13:48:00 -0000 [thread overview]
Message-ID: <696945e9-4942-5285-0bb4-0bf899606f0a@simark.ca> (raw)
In-Reply-To: <20190306102006.99150-1-alan.hayward@arm.com>
On 2019-03-06 5:20 a.m., Alan Hayward wrote:
> Recent versions of Ubuntu and Debian default GCC to enable pie.
>
> In dump.exp, pie will causes addresses to be out of range for IHEX.
>
> In break-interp.exp, pie is explicitly set for some tests and assumed
> to be disabled for the remainder.
>
> Ensure pie is disabled for these tests when required.
>
> gdb/testsuite/ChangeLog:
>
> 2019-03-06 Alan Hayward <alan.hayward@arm.com>
>
> * gdb.base/break-interp.exp: Ensure pie is disabled.
> * gdb.base/dump.exp: Likewise.
Hi Alan,
The "nopie" flag to gdb_compile has been introduced recently for this,
could you use that instead? See commit 6e8b1ab2fd4c ("Fix various tests
to use -no-pie linker flag when needed").
> ---
> gdb/testsuite/gdb.base/break-interp.exp | 4 ++++
> gdb/testsuite/gdb.base/dump.exp | 4 ++++
> 2 files changed, 8 insertions(+)
>
> diff --git a/gdb/testsuite/gdb.base/break-interp.exp b/gdb/testsuite/gdb.base/break-interp.exp
> index f85e8a650a..409c31e568 100644
> --- a/gdb/testsuite/gdb.base/break-interp.exp
> +++ b/gdb/testsuite/gdb.base/break-interp.exp
> @@ -627,6 +627,10 @@ foreach ldprelink {NO YES} {
> if {$binpie != "NO"} {
> lappend opts {additional_flags=-fPIE}
> lappend opts {ldflags=-pie}
> + } else {
> + # Recent Debian/Ubuntu defaults PIE enabled. Ensure it is disabled.
> + lappend opts {additional_flags=-no-pie}
> + lappend opts {ldflags=-no-pie}
> }
I believe it won't be necessary here to change CFLAGS (which
additional_flags does), only ldflags, to make the final executable a
non-PIE. Anyway, you'll probably end up using the "nopie" gdb_compile flag.
>
> set dir ${exec}.d
> diff --git a/gdb/testsuite/gdb.base/dump.exp b/gdb/testsuite/gdb.base/dump.exp
> index 44b0988b80..b2d7ef938a 100644
> --- a/gdb/testsuite/gdb.base/dump.exp
> +++ b/gdb/testsuite/gdb.base/dump.exp
> @@ -36,6 +36,10 @@ if {[istarget "spu*-*-*"]} then {
> set is64bitonly "yes"
> }
>
> +# Ensure -pie is disabled as this breaks IHEX tests.
Can you just precise how it breaks the IHEX tests, as you did in the
commit message (it causes the addresses to be out of range for that format)?
This patch is ok with those fixed, thanks!
Simon
next prev parent reply other threads:[~2019-03-19 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 10:20 Alan Hayward
2019-03-19 10:45 ` [PING][PATCH] " Alan Hayward
2019-03-19 13:48 ` Simon Marchi [this message]
2019-03-19 15:45 ` [PATCH] " Alan Hayward
2019-03-19 16:07 ` Simon Marchi
2019-03-20 10:36 ` Alan Hayward
2019-03-19 16:36 ` Pedro Alves
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=696945e9-4942-5285-0bb4-0bf899606f0a@simark.ca \
--to=simark@simark.ca \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.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