aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2025-03-10 15:11:25 -0600
committerTom Tromey <tom@tromey.com>2025-03-10 15:11:25 -0600
commitd03f69e74638f0515a0fb391ca1c74764dc79b9a (patch)
treeaa866386d96bd6a737b634e39b9ee61ef622c536
parent2609ee6f193505ec96552a9c33ecdea679242114 (diff)
downloadbinutils-d03f69e74638f0515a0fb391ca1c74764dc79b9a.zip
binutils-d03f69e74638f0515a0fb391ca1c74764dc79b9a.tar.gz
binutils-d03f69e74638f0515a0fb391ca1c74764dc79b9a.tar.bz2
Remove pid from test name in gcore-memory-usage.exp
The new gcore-memory-usage.exp test puts a PID into a test case name, causing spurious comparison failures. This patch changes the test name to avoid this.
-rw-r--r--gdb/testsuite/gdb.base/gcore-memory-usage.exp2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.base/gcore-memory-usage.exp b/gdb/testsuite/gdb.base/gcore-memory-usage.exp
index db7f270..bd041f2 100644
--- a/gdb/testsuite/gdb.base/gcore-memory-usage.exp
+++ b/gdb/testsuite/gdb.base/gcore-memory-usage.exp
@@ -57,7 +57,7 @@ proc run_test {megs} {
set inferior_pid [spawn_id_get_pid $inferior_spawn_id]
set gdb_pid [exp_pid -i [board_info host fileid]]
- gdb_test "attach $inferior_pid" "Attaching to.*"
+ gdb_test "attach $inferior_pid" "Attaching to.*" attach
set line [gdb_get_line_number "TAG: BREAK HERE" $::testfile.c]
gdb_breakpoint "${::srcfile}:$line" "break at to known line"
gdb_continue_to_breakpoint "continue to known line"