FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

gdb: ensure test_name is initialized in gdb_breakpoint

Browse source 
A refactoring in 4b9728bec1 (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>
This commit is contained in:
Lancelot SIX 2023-01-04 17:58:08 +00:00
parent d654ad96eb
commit 4036ad07f4
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
gdb/testsuite/lib/gdb.exp
View file

@ -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 $" {}