[pushed] Remove pid from test name in gcore-memory-usage.exp

Message ID 20250310211943.2445824-1-tom@tromey.com
State New
Headers
Series [pushed] Remove pid from test name in gcore-memory-usage.exp |

Checks

Context Check Description
linaro-tcwg-bot/tcwg_gdb_build--master-arm fail Patch failed to apply
linaro-tcwg-bot/tcwg_gdb_build--master-aarch64 fail Patch failed to apply

Commit Message

Tom Tromey March 10, 2025, 9:19 p.m. UTC
  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.
---
 gdb/testsuite/gdb.base/gcore-memory-usage.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
  

Patch

diff --git a/gdb/testsuite/gdb.base/gcore-memory-usage.exp b/gdb/testsuite/gdb.base/gcore-memory-usage.exp
index db7f270a5e8..bd041f2d1a8 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"