Update copyright year range in all GDB files.

[deliverable/binutils-gdb.git] / gdb / testsuite / gdb.threads / manythreads.exp

diff --git a/gdb/testsuite/gdb.threads/manythreads.exp b/gdb/testsuite/gdb.threads/manythreads.exp
index c35d6ab2f31d30b601fdffb3ae4e3952fff2f393..2148c6501adacc69337f2132810d4a9481c2b019 100644 (file)
--- a/gdb/testsuite/gdb.threads/manythreads.exp
+++ b/gdb/testsuite/gdb.threads/manythreads.exp
@@ -1,5 +1,5 @@
 # manythreads.exp -- Expect script to test stopping many threads
-# Copyright (C) 2004-2014 Free Software Foundation, Inc.
+# Copyright (C) 2004-2020 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -16,6 +16,11 @@
 
 # This file was written by Jeff Johnston. (jjohnstn@redhat.com)
 
+# This test requires sending ^C to interrupt the running target.
+if [target_info exists gdb,nointerrupts] {
+    verbose "Skipping manythreads.exp because of nointerrupts."
+    return
+}
 
 standard_testfile
 
@@ -35,11 +40,7 @@ runto_main
 
 # We'll need this when we send_gdb a ^C to GDB.  Need to do it before we
 # run the program and gdb starts saving and restoring tty states.
-# On Ultrix, we don't need it and it is really slow (because shell_escape
-# doesn't use vfork).
-if ![istarget "*-*-ultrix*"] then {
-    gdb_test "shell stty intr '^C'" ".*"
-}
+gdb_test "shell stty intr '^C'" ".*"
 
 set message "first continue"
 gdb_test_multiple "continue" "first continue" {
@@ -69,14 +70,14 @@ proc interrupt_and_wait { message } {
        -re "\\\[\[^\]\]* exited\\\]\r\n" {
            exp_continue
        }
-       -re "Program received signal SIGINT.*$gdb_prompt $" {
+       -re " received signal SIGINT.*$gdb_prompt $" {
            pass "$message"
        }
        -re "$gdb_prompt $" {
            # Note that with this regex order, if GDB emits [New
-           # Thread ...] output between "Program received signal" and
-           # the prompt, the "Program received signal" regex won't
-           # match.  That's good, as if we see that happening, it's a
+           # Thread ...] output between "Thread NNN received signal"
+           # and the prompt, the "received signal" regex won't match.
+           # That's good, as if we see that happening, it's a
            # regression.
            #
            # GDB makes sure to notify about signal stops, end of
@@ -91,7 +92,7 @@ proc interrupt_and_wait { message } {
            #  ... more new threads output ...
            #  [New Thread NNN]
            #  [New Thread NNN]
-           #  Program received signal SIGINT, Interrupt.
+           #  Thread NNN received signal SIGINT, Interrupt.
            #  [New Thread NNN]
            #  [New Thread NNN]
            #  ... pages of new threads output ...
@@ -99,7 +100,7 @@ proc interrupt_and_wait { message } {
            #  foo () at foo.c:31
            #  31      bar ();
            #
-           fail $test
+           fail $message
        }
     }
 }
@@ -150,7 +151,7 @@ remote_expect host 1 {
   -re "\\\[\[^\]\]* exited\\\]\r\n" {
     exp_continue -continue_timer
   }
-  -re "Program received signal SIGINT.*$gdb_prompt $" {
+  -re " received signal SIGINT.*$gdb_prompt $" {
     if { $failed == 0 } {
       fail "check for duplicate SIGINT"
     }