Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Hayward <Alan.Hayward@arm.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: nd <nd@arm.com>
Subject: [PING][PATCH] Testsuite: Ensure pie is disabled on some tests
Date: Tue, 19 Mar 2019 10:45:00 -0000	[thread overview]
Message-ID: <1880525A-E1A5-4707-AEB2-F8DF1FA9BCBA@arm.com> (raw)
In-Reply-To: <20190306102006.99150-1-alan.hayward@arm.com>

Ping for this.


> On 6 Mar 2019, at 10:20, Alan Hayward <Alan.Hayward@arm.com> 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.
> ---
> 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}
> 			    }
> 
> 			    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.
> +# (PIE defaults to enabled on recent Debian/Ubuntu).
> +lappend options "additional_flags=-no-pie"
> +
> if  { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable ${options}] != "" } {
>      untested "failed to compile"
>      return -1
> -- 
> 2.17.2 (Apple Git-113)
> 


  reply	other threads:[~2019-03-19 10:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 10:20 [PATCH] " Alan Hayward
2019-03-19 10:45 ` Alan Hayward [this message]
2019-03-19 13:48 ` Simon Marchi
2019-03-19 15:45   ` 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=1880525A-E1A5-4707-AEB2-F8DF1FA9BCBA@arm.com \
    --to=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