aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.server/exit-multiple-threads.exp
blob: 46239e3eabf3e8a6b73bbea0ea8ce8e91cbd44f8 (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
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
# This testcase is part of GDB, the GNU debugger.
#
# Copyright 2020-2023 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 GDB can handle receiving the W and X packets for a target
# with multiple threads, but only a single inferior.
#
# Specifically, check GDB handles this case where multi-process
# extensions are turned off.  At one point this was causing GDB to
# give a warning when the exit arrived that the remote needed to
# include a thread-id, which was not correct.

load_lib gdbserver-support.exp

require allow_gdbserver_tests

standard_testfile

# Start up GDB and GDBserver debugging EXECUTABLE.  When
# DISABLE_MULTI_PROCESS is true then disable GDB's remote
# multi-process support, otherwise, leave it enabled.
#
# Places a breakpoint in function 'breakpt' and then continues to the
# breakpoint, at which point it runs 'info threads'.
proc prepare_for_test { executable disable_multi_process } {
    global GDBFLAGS

    save_vars { GDBFLAGS } {
	# If GDB and GDBserver are both running locally, set the sysroot to avoid
	# reading files via the remote protocol.
	if { ![is_remote host] && ![is_remote target] } {
	    set GDBFLAGS "$GDBFLAGS -ex \"set sysroot\""
	}

	clean_restart ${executable}
    }

    # Make sure we're disconnected, in case we're testing with an
    # extended-remote board, therefore already connected.
    gdb_test "disconnect" ".*"

    # Disable XML-based thread listing, and possible the multi-process
    # extensions.
    gdb_test_no_output "set remote threads-packet off"
    if { $disable_multi_process } {
	gdb_test_no_output "set remote multiprocess-feature-packet off"
    }

    # Start gdbserver and connect.
    set res [gdbserver_start "" $executable]
    set gdbserver_protocol [lindex $res 0]
    set gdbserver_gdbport [lindex $res 1]
    set res [gdb_target_cmd $gdbserver_protocol $gdbserver_gdbport]
    if ![gdb_assert {$res == 0} "connect"] {
	return
    }

    # Run until we hit the breakpt function, then list all threads.
    gdb_breakpoint "breakpt"
    gdb_continue_to_breakpoint "breakpt"
    gdb_test "info threads" ".*"
}

# Run the tests where the inferior exits normally (the W packet) while
# we have multiple-threads.  EXECUTABLE is the binary under test, and
# DISABLE_MULTI_PROCESS indicates if we should disable GDB's remote
# multi-process support.
proc run_exit_test { executable disable_multi_process } {
    global decimal

    prepare_for_test ${executable} ${disable_multi_process}

    # Finally, continue until the process exits, ensure we don't see
    # any warnings between "Continuing." and the final process has
    # exited message.
    if { $disable_multi_process } {
	set process_pattern "Remote target"
    } else {
	set process_pattern "process $decimal"
    }
    gdb_test "continue" \
	[multi_line \
	     "Continuing\\." \
	     "\\\[Inferior $decimal \\\(${process_pattern}\\\) exited normally\\\]" ] \
	"continue until process exits"
}

# Run the tests where the inferior exits with a signal (the X packet)
# while we have multiple-threads.  EXECUTABLE is the binary under
# test, and DISABLE_MULTI_PROCESS indicates if we should disable GDB's
# remote multi-process support.
proc run_signal_test { executable disable_multi_process } {
    global decimal gdb_prompt

    prepare_for_test ${executable} ${disable_multi_process}

    set inf_pid [get_valueof "/d" "global_pid" "unknown"]
    gdb_assert ![string eq ${inf_pid} "unknown"] "read the pid"

    # This sets the inferior running again, with all threads going
    # into a long delay loop.
    send_gdb "continue\n"

    # Send the inferior a signal to kill it.
    sleep 1
    remote_exec target "kill -9 ${inf_pid}"

    # Process the output from GDB.
    gdb_test_multiple "" "inferior exited with signal" {
	-re "Continuing\\.\r\n\r\nProgram terminated with signal SIGKILL, Killed.\r\nThe program no longer exists.\r\n$gdb_prompt $" {
	    pass $gdb_test_name
	}
    }
}

# Run all of the tests.
foreach_with_prefix test { exit signal } {
    set def "DO_[string toupper $test]_TEST"
    set func "run_${test}_test"

    set executable "$binfile-${test}"
    if [build_executable "failed to prepare" $executable $srcfile \
	    [list debug pthreads additional_flags=-D${def}]] {
	return -1
    }

    foreach_with_prefix multi_process { 0 1 } {
	$func ${executable} ${multi_process}
    }
}