aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@polymtl.ca>2023-01-05 11:23:45 -0500
committerSimon Marchi <simon.marchi@polymtl.ca>2023-01-05 11:36:05 -0500
commitcabd67874a6ef7aaed41490d9eaddc4a4869a452 (patch)
tree6725db9866b13f8a92a9e4136bf5b0be8ef910e2 /gdb/testsuite
parent954a1f9183c68671c07f21baf78ac2053390af55 (diff)
downloadfsf-binutils-gdb-cabd67874a6ef7aaed41490d9eaddc4a4869a452.zip
fsf-binutils-gdb-cabd67874a6ef7aaed41490d9eaddc4a4869a452.tar.gz
fsf-binutils-gdb-cabd67874a6ef7aaed41490d9eaddc4a4869a452.tar.bz2
gdb/testsuite: add back needed -re clause in gdb_breakpoint
Commit 4b9728be ("gdb: use gdb_test_multiple in gdb_breakpoint") caused, amongst others: (gdb) break 1^M No line 1 in the current file.^M Make breakpoint pending on future shared library load? (y or [n]) n^M (gdb) FAIL: gdb.dwarf2/dw2-main-no-line-number.exp: gdb_breakpoint: set breakpoint at 1 FAIL: gdb.dwarf2/dw2-main-no-line-number.exp: !$breakpoint_at_missing_lineno_set This is because it removed one empty -re clause (matching just the prompt) that is necessary after replying "n" to the pending breakpoint question. Add this clause back. Change-Id: Ibfaa059d58bbea660bc29f0547e2f75c323fcbc6 Approved-By: Tom de Vries <tdevries@suse.de>
Diffstat (limited to 'gdb/testsuite')
-rw-r--r--gdb/testsuite/lib/gdb.exp6
1 files changed, 6 insertions, 0 deletions
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index e17eace..af538e5 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -657,6 +657,12 @@ proc gdb_breakpoint { linespec args } {
send_gdb "$pending_response\n"
exp_continue
}
+ -re "$gdb_prompt $" {
+ if { $print_fail } {
+ fail $test_name
+ }
+ return 0
+ }
}
if { $print_pass } {
pass $test_name