blob: 89c9a92c9df9984e142799b0d64f5116bfd3d9d3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
# Copyright 2016 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
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
# Test that on a separate MI UI (new-ui mi <tty>), the printing of an
# asynchronous event (e.g. =library-loaded) during the synchronous
# execution of a command (e.g. -exec-run or -exec-continue) does not
# prematurely re-enable MI input. After executing synchronous
# commands, MI should not process further commands until the inferior
# stops again. See PR gdb/20418.
load_lib mi-support.exp
standard_testfile
if {[build_executable $testfile.exp $testfile ${srcfile} "debug"] == -1} {
untested "failed to compile"
return -1
}
# The test driver. SYNC_COMMAND specifies which command is used to
# synchronously start the program running.
proc do_test {sync_command} {
global srcdir subdir binfile srcfile
global gdb_spawn_id gdb_main_spawn_id mi_spawn_id inferior_spawn_id
global gdb_prompt mi_gdb_prompt
mi_gdb_exit
if {[mi_gdb_start "separate-mi-tty"] != 0} {
fail "could not start gdb"
return
}
mi_delete_breakpoints
mi_gdb_reinitialize_dir $srcdir/$subdir
mi_gdb_load $binfile
# Start a synchronous run/continue on the MI UI.
set test "send synchronous execution command"
if {$sync_command == "run"} {
if {[mi_run_cmd] >= 0} {
pass $test
} else {
return
}
} else {
if {[mi_runto main] < 0} {
return
}
if {[mi_send_resuming_command_raw "123-exec-continue" $test] >= 0} {
pass $test
} else {
return
}
}
# Send -thread-info immediately after. If everything works
# correctly, this is only serviced by GDB when the execution
# stops.
send_gdb "456-thread-info\n"
pass "send -thread-info"
# Make sure we trigger an asynchronous event (=thread-group-added)
# in the separate MI UI. Note the "run" variant usually triggers
# =thread-group-started/=thread-created/=library-loaded as well.
with_spawn_id $gdb_main_spawn_id {
gdb_test "add-inferior" "Added inferior 2"
}
# Interrupt the program.
with_spawn_id $gdb_main_spawn_id {
set message "interrupt on the CLI"
gdb_test_multiple "interrupt" "$message" {
-re "$gdb_prompt " {
gdb_test_multiple "" "$message" {
-re "received signal SIGINT" {
pass $message
}
}
}
}
}
# On the MI channel, we should see the interrupt output _before_
# the -thread-info output.
with_spawn_id $mi_spawn_id {
mi_expect_interrupt "got MI interrupt output"
}
# Look for the result of our -thread-info. If input were
# re-enabled too soon, the thread would incorrectly show up with
# state="running".
with_spawn_id $mi_spawn_id {
mi_gdb_test "" "456\\^.*state=\"stopped\".*" \
"got -thread-info output and thread is stopped"
}
}
foreach_with_prefix sync-command {"run" "continue"} {
do_test ${sync-command}
}
|
GitWeb