Adjust gdb.base/bp-permanent.exp for Cygwin

On Cygwin, all inferiors are multi-threaded, because both Windows and
the Cygwin runtime spawn a few helper threads.  Adjust the
gdb.base/bp-permanent.exp testcase to work with either single- or
multi-threaded inferiors.

Approved-by: Kevin Buettner <kevinb@redhat.com>
Change-Id: I28935b34fc9f739c2a5490e83aa4995d29927be2

diff --git a/gdb/testsuite/gdb.base/bp-permanent.exp b/gdb/testsuite/gdb.base/bp-permanent.exp
index 62ce3f69b6998f7c1ffe37c9f708a7b25e678df1..c6c62699043d08c894820ef9a775a4b1c8c3b3c6 100644 (file)
--- a/gdb/testsuite/gdb.base/bp-permanent.exp
+++ b/gdb/testsuite/gdb.base/bp-permanent.exp
@@ -134,7 +134,7 @@ proc test {always_inserted sw_watchpoint} {
                unsupported "failed to stop at permanent breakpoint"
                return
            }
-           -re "Program received signal SIGTRAP.*$gdb_prompt $" {
+           -re "received signal SIGTRAP.*$gdb_prompt $" {
                pass $test
            }
        }
@@ -174,7 +174,7 @@ proc test {always_inserted sw_watchpoint} {
        # disabled, it should act as if we hadn't created it in the first
        # place.  IOW, we should get a random signal, and, the breakpoint's
        # command should not run.
-       gdb_test "continue" "Program received signal SIGTRAP.*" \
+       gdb_test "continue" "received signal SIGTRAP.*" \
            "disabled permanent breakpoint doesn't explain stop"
 
        gdb_test "info breakpoints" \