aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-06-13 17:29:37 +0200
committerTom de Vries <tdevries@suse.de>2024-06-13 17:29:37 +0200
commit56c82e7029464dbd8b2b7237bf3176f3199f9e71 (patch)
tree75a604539c4e36ba660353f199d4f378c0b37a8d
parente8e10743f7b207b21a1efb0cc9e42487080db013 (diff)
downloadgdb-56c82e7029464dbd8b2b7237bf3176f3199f9e71.zip
gdb-56c82e7029464dbd8b2b7237bf3176f3199f9e71.tar.gz
gdb-56c82e7029464dbd8b2b7237bf3176f3199f9e71.tar.bz2
[gdb/testsuite] Fix kfail number in gdb.base/watchpoint-running.exp
Test-case gdb.base/watchpoint-running.exp reports the following kfail: ... KFAIL: $exp: all-stop: software: watchpoint hit (timeout) (PRMS: gdb/111111) ... but the referenced gdb PR doesn't exist. Fix this by using an actual PR. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31833
-rw-r--r--gdb/testsuite/gdb.base/watchpoint-running.exp2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.base/watchpoint-running.exp b/gdb/testsuite/gdb.base/watchpoint-running.exp
index c3aae30..abba43f 100644
--- a/gdb/testsuite/gdb.base/watchpoint-running.exp
+++ b/gdb/testsuite/gdb.base/watchpoint-running.exp
@@ -105,7 +105,7 @@ proc test {stop_mode hw} {
# GDB should transparently temporarily pause the inferior,
# to force it to single step, but it doesn't, so the
# thread continues running free.
- setup_kfail gdb/111111 *-*-*
+ setup_kfail gdb/31833 *-*-*
# No point waiting too much for output we know isn't
# coming.