]> git.ipfire.org Git - thirdparty/binutils-gdb.git/blame - gdb/testsuite/gdb.base/interrupt-noterm.exp
Update copyright year range in all GDB files
[thirdparty/binutils-gdb.git] / gdb / testsuite / gdb.base / interrupt-noterm.exp
CommitLineData
3666a048 1# Copyright (C) 2013-2021 Free Software Foundation, Inc.
6f64ef53
PA
2
3# This program is free software; you can redistribute it and/or modify
4# it under the terms of the GNU General Public License as published by
5# the Free Software Foundation; either version 3 of the License, or
6# (at your option) any later version.
7#
8# This program is distributed in the hope that it will be useful,
9# but WITHOUT ANY WARRANTY; without even the implied warranty of
10# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
11# GNU General Public License for more details.
12#
13# You should have received a copy of the GNU General Public License
14# along with this program. If not, see <http://www.gnu.org/licenses/>.
15
16standard_testfile
17
18if [prepare_for_testing "failed to prepare for testing" \
19 ${testfile} ${srcfile} {debug}] {
20 return -1
21}
22
23# Pretend there's no terminal.
24gdb_test_no_output "set interactive-mode off"
6f64ef53 25
50441f0f 26if ![runto_main] {
bc6c7af4 27 fail "can't run to main"
6f64ef53
PA
28 return -1
29}
30
31# Delete breakpoints so that the next resume is a plain continue,
32# instead of a step-over-breakpoint sequence just while GDB sends the
33# interrupt request. If that's buggy on some targets (and it was on
34# target remote for a while, where a ctrl-c at the wrong time will get
35# lost), then it should get its own specific test. Disable
36# confirmation, avoiding complications caused by the fact that we've
37# disabled the terminal -- GDB would auto-answer "yes", confusing
38# gdb_test_multiple.
39gdb_test_no_output "set confirm off"
40gdb_test_no_output "delete"
41gdb_test_no_output "set confirm on"
42
43set async_supported -1
44set test "continue &"
45gdb_test_multiple $test $test {
46 -re "Continuing\\.\r\n$gdb_prompt $" {
47 set async_supported 1
48 pass $test
49 }
50 -re ".*Asynchronous execution not supported on this target..*" {
51 unsupported $test
52 }
53}
54if { $async_supported < 0 } {
55 return 1
56}
57
58# With native debugging, and no terminal (emulated by interactive-mode
59# off, above), GDB had a bug where "interrupt" would send SIGINT to
60# its own process group, instead of the inferior's.
61set test "interrupt"
62gdb_test_multiple $test $test {
63 -re "interrupt\r\n$gdb_prompt " {
64 pass $test
65 }
66}
67
68set test "inferior received SIGINT"
69gdb_test_multiple "" $test {
70 -re "\r\nProgram received signal SIGINT.*" {
71 # This appears after the prompt, which was already consumed
72 # above.
73 pass $test
74 }
75}