[PUSHED] gdb/testsuite: Avoid leaking a port number into results summary

Andrew Burgess andrew.burgess@embecosm.com
Thu Feb 6 16:43:00 GMT 2020


Give a test a real name in order to avoid including a port number in
the results summary file - which makes comparing test results between
runs hard.

gdb/testsuiteChangeLog:

	* gdb.server/multi-ui-errors.exp: Give a test a real name to avoid
	including a port number in the output.

Change-Id: I19334e176ac15aee2a9732a6060c58153d9fb793
---
 gdb/testsuite/ChangeLog                      | 5 +++++
 gdb/testsuite/gdb.server/multi-ui-errors.exp | 3 ++-
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.server/multi-ui-errors.exp b/gdb/testsuite/gdb.server/multi-ui-errors.exp
index c2a05b0fb6f..9d64a9a245b 100644
--- a/gdb/testsuite/gdb.server/multi-ui-errors.exp
+++ b/gdb/testsuite/gdb.server/multi-ui-errors.exp
@@ -65,7 +65,8 @@ with_spawn_id $extra_spawn_id {
 
 # Connect to the remote and continue its execution from the other UI.
 with_spawn_id $extra_spawn_id {
-    gdb_test "target $gdbserver_protocol $gdbserver_gdbport" ".*"
+    gdb_test "target $gdbserver_protocol $gdbserver_gdbport" ".*" \
+	"connect to gdbserver"
     send_gdb "continue\n"
 }
 
-- 
2.14.5



More information about the Gdb-patches mailing list