This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
make pending-step.exp testable with "set debug infrun 1"
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Date: Mon, 6 Jun 2011 14:39:15 +0100
- Subject: make pending-step.exp testable with "set debug infrun 1"
I ran the pending-step.exp test with "set debug infrun 1" enabled,
and it reported a false fail:
FAIL: gdb.threads/pending-step.exp: next in multiple threads with breakpoints (spurious SIGTRAP)
The SIGTRAP regex was matching things like:
infrun: target_wait (-1, status) =
infrun: 26696 [process 26696],
infrun: status->kind = stopped, signal = SIGTRAP
...
(gdb)
Since I wrote this, I figure it doesn't hurt putting it in.
Applied.
--
Pedro Alves
2011-06-06 Pedro Alves <pedro@codesourcery.com>
gdb/testsuite/
* gdb.threads/pending-step.exp: Add more context to SIGTRAP match.
---
gdb/testsuite/gdb.threads/pending-step.exp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: src/gdb/testsuite/gdb.threads/pending-step.exp
===================================================================
--- src.orig/gdb/testsuite/gdb.threads/pending-step.exp 2011-06-06 14:29:26.698861968 +0100
+++ src/gdb/testsuite/gdb.threads/pending-step.exp 2011-06-06 14:31:29.488862010 +0100
@@ -77,7 +77,7 @@ set ok 0
for {set i 0} {$i < $iterations} {incr i} {
set ok 0
gdb_test_multiple "next" "$test" {
- -re "SIGTRAP.*$gdb_prompt $" {
+ -re "Program received signal SIGTRAP.*$gdb_prompt $" {
fail "$test (spurious SIGTRAP)"
}
-re "$gdb_prompt $" {