From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [PATCH] Prevent appending "-g" after "-g3" to compile options in info-macros.exp.
Date: Wed, 15 Jan 2014 12:46:00 -0000 [thread overview]
Message-ID: <87fvop2z0u.fsf@br87z6lw.de.ibm.com> (raw)
In-Reply-To: <87d2juwj2x.fsf@fleche.redhat.com> (Tom Tromey's message of "Tue, 14 Jan 2014 10:48:22 -0700")
On Tue, Jan 14 2014, Tom Tromey wrote:
>>>>>> "Andreas" == Andreas Arnez <arnez@linux.vnet.ibm.com> writes:
>
> Andreas> 2014-01-14 Andreas Arnez <arnez@linux.vnet.ibm.com>
> Andreas> * gdb.base/info-macros.exp: Remove "debug" from the compile
> Andreas> options.
>
> Andreas> -set options "debug additional_flags=-g3"
> Andreas> +set options "additional_flags=-g3"
>
> Would you mind adding a comment explaining why "debug" doesn't appear
> here? Ok with that.
Sure. How about this?
-----
Subject: [PATCH] Prevent appending "-g" after "-g3" to compile options
in info-macros.exp.
When upstream gcc is given a command line with "-g3" followed by "-g",
it doesn't generate a ".debug_macro" section. This is because the last
option wins, thus downgrading the debug level again. Without any macro
debug information in the executable, info-macros.exp obviously yields
many failures.
Since "-g" is appended by DejaGnu's target_compile whenever the "debug"
option is set, the fix just removes that option.
testsuite/
2014-01-15 Andreas Arnez <arnez@linux.vnet.ibm.com>
* gdb.base/info-macros.exp: Remove "debug" from the compile
options.
---
gdb/testsuite/gdb.base/info-macros.exp | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/gdb/testsuite/gdb.base/info-macros.exp b/gdb/testsuite/gdb.base/info-macros.exp
index ff889f4..798d9b5 100644
--- a/gdb/testsuite/gdb.base/info-macros.exp
+++ b/gdb/testsuite/gdb.base/info-macros.exp
@@ -27,7 +27,9 @@ if ![test_compiler_info gcc*] {
return -1
}
-set options "debug additional_flags=-g3"
+# Don't use "debug" here. Otherwise "-g" would be appended to the gcc
+# command line, possibly overriding "-g3" (depending on gcc version).
+set options "additional_flags=-g3"
if { [prepare_for_testing ${testfile}.exp ${testfile} ${srcfile} $options] } {
untested ${testfile}.exp
--
1.8.3.1
next prev parent reply other threads:[~2014-01-15 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 17:44 Andreas Arnez
2014-01-14 17:48 ` Tom Tromey
2014-01-15 12:46 ` Andreas Arnez [this message]
2014-01-15 15:08 ` Tom Tromey
2014-01-22 16:10 ` Andreas Krebbel
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=87fvop2z0u.fsf@br87z6lw.de.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
--cc=uweigand@de.ibm.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