Blame SOURCES/gdb-testsuite-readline63-sigint-revert.patch

190f2a
diff --git b/gdb/testsuite/gdb.gdb/selftest.exp a/gdb/testsuite/gdb.gdb/selftest.exp
190f2a
index 7e6a4e1..969797a 100644
190f2a
--- b/gdb/testsuite/gdb.gdb/selftest.exp
190f2a
+++ a/gdb/testsuite/gdb.gdb/selftest.exp
190f2a
@@ -451,25 +451,9 @@ proc test_with_self { executable } {
190f2a
     }
190f2a
     
190f2a
     set description "send SIGINT signal to child process"
190f2a
-    gdb_test_multiple "signal SIGINT" "$description" {
190f2a
-	-re "^signal SIGINT\r\nContinuing with signal SIGINT.\r\nQuit\r\n" {
190f2a
-	    pass "$description"
190f2a
-	}
190f2a
-    }
190f2a
-
190f2a
-    set description "send ^C to child process again"
190f2a
-    send_gdb "\003"
190f2a
-    gdb_expect {
190f2a
-	-re "(Thread .*|Program) received signal SIGINT.*$gdb_prompt $" {
190f2a
-	    pass "$description"
190f2a
-	}
190f2a
-	-re ".*$gdb_prompt $" {
190f2a
-	    fail "$description"
190f2a
-	}
190f2a
-	timeout {
190f2a
-	    fail "$description (timeout)"
190f2a
-	}
190f2a
-    }
190f2a
+    gdb_test "signal SIGINT" \
190f2a
+	"Continuing with signal SIGINT.*" \
190f2a
+	"$description"
190f2a
 
190f2a
     # Switch back to the GDB thread if Guile support is linked in.
190f2a
     # "signal SIGINT" could also switch the current thread.