[binutils-gdb] gdb: ensure test_name is initialized in gdb_breakpoint

[binutils-gdb] gdb: ensure test_name is initialized in gdb_breakpoint

[Lancelot SIX]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4036ad07f4293ca5cd9bd9cf95fc5d8b86d6e1a6

commit 4036ad07f4293ca5cd9bd9cf95fc5d8b86d6e1a6
Author: Lancelot SIX <lancelot.six@amd.com>
Date:   Wed Jan 4 17:58:08 2023 +0000

    gdb: ensure test_name is initialized in gdb_breakpoint
    
    A refactoring in 4b9728bec15 (gdb: use gdb_test_multiple in
    gdb_breakpoint) left the $test_name variable undefined.
    
    This patch fixes this.
    
    Approved-By: Simon Marchi <simon.marchi@efficios.com>

Diff:
---
 gdb/testsuite/lib/gdb.exp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index ba16b2ab315..e17eace4cb1 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -639,8 +639,9 @@ proc gdb_breakpoint { linespec args } {
 	set print_pass 1
     }
 
+    set test_name "gdb_breakpoint: set breakpoint at $linespec"
     # The first two regexps are what we get with -g, the third is without -g.
-    gdb_test_multiple "$break_command $linespec" "gdb_breakpoint: set breakpoint at $linespec" {
+    gdb_test_multiple "$break_command $linespec" $test_name {
 	-re "$break_message \[0-9\]* at .*: file .*, line $decimal.\r\n$gdb_prompt $" {}
 	-re "$break_message \[0-9\]*: file .*, line $decimal.\r\n$gdb_prompt $" {}
 	-re "$break_message \[0-9\]* at .*$gdb_prompt $" {}