From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [committed][gdb/testsuite] Fix DUPLICATE in gdb.base/load-command.exp
Date: Fri, 24 Sep 2021 12:40:24 +0200 [thread overview]
Message-ID: <20210924104023.GA1480@delia> (raw)
Hi,
Fix this duplicate:
...
DUPLICATE: gdb.base/load-command.exp: check initial value of the_variable
...
by using with_test_prefix.
Tested on x86_64-linux.
Committed to trunk.
Thanks,
- Tom
[gdb/testsuite] Fix DUPLICATE in gdb.base/load-command.exp
---
gdb/testsuite/gdb.base/load-command.exp | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/gdb/testsuite/gdb.base/load-command.exp b/gdb/testsuite/gdb.base/load-command.exp
index 8847aff3b74..944dc39c155 100644
--- a/gdb/testsuite/gdb.base/load-command.exp
+++ b/gdb/testsuite/gdb.base/load-command.exp
@@ -42,8 +42,12 @@ gdb_test "print/x the_variable" " = 0x1234" "check initial value of the_variable
gdb_test_no_output "set the_variable = 0x5555" "manually change the_variable"
gdb_test "print/x the_variable" " = 0x5555" "check manually changed value of the_variable"
-# Re-load the binary using the load command.
-gdb_test "load ${binfile}" ".*Loading section .data.*Transfer rate:.*" "re-load binary"
-
-# Re-loading the binary should have reset the variable value.
-gdb_test "print/x the_variable" " = 0x1234" "check initial value of the_variable"
+with_test_prefix "reload" {
+ # Re-load the binary using the load command.
+ gdb_test "load ${binfile}" ".*Loading section .data.*Transfer rate:.*" \
+ "re-load binary"
+
+ # Re-loading the binary should have reset the variable value.
+ gdb_test "print/x the_variable" " = 0x1234" \
+ "check initial value of the_variable"
+}
reply other threads:[~2021-09-24 10:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210924104023.GA1480@delia \
--to=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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