blob: 3d73c2e7ce6750ba63e117929b9f273ebfaf5447 (
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
|
# This testcase is part of GDB, the GNU debugger.
# Copyright 2022-2024 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 starting gdbserver using the 'target remove | ....' syntax.
# The extended-remote target type is tested too. The test checks that
# the `|` character can be seen in the 'info connections' output, and
# (when Python is available) in the gdb.TargetConnection.details
# string.
# This test relies on starting gdbserver using the pipe syntax. Not
# sure how well this will run if part of this test is being run
# elsewhere.
require {!is_remote target} {!is_remote host}
load_lib gdbserver-support.exp
standard_testfile
require allow_gdbserver_tests
set gdbserver [find_gdbserver]
if { $gdbserver == "" } {
unsupported "could not find gdbserver"
return
}
standard_testfile normal.c
set executable ${testfile}
if {[build_executable "failed to prepare" $testfile $srcfile debug]} {
return -1
}
# Start GDB using remote type TARGET, which should be either "remote"
# or "extended-remote". Check the output of 'info connections', and
# the contents of the gdb.TargetConnection.details string.
proc do_test { target } {
global timeout
clean_restart ${::binfile}
# Make sure we're disconnected, in case we're testing with an
# extended-remote board, therefore already connected.
gdb_test "disconnect" ".*" "disconnect before running the test"
gdb_test "target ${target} | ${::gdbserver} - ${::binfile}" ".*" \
"start gdbserver using pipe syntax"
gdb_breakpoint main
gdb_continue_to_breakpoint main
gdb_test "info frame" ".* in main .*"
gdb_test "info connections" "${target} \| ${::gdbserver} - ${::binfile} \[^\r\n\]+"
if { [allow_python_tests] } {
gdb_test_no_output "python conn = gdb.selected_inferior().connection"
gdb_test "python print(conn.details)" "\| ${::gdbserver} - ${::binfile}"
}
# Make sure GDB server doesn't attempt to reconnect with a closed STDIN.
# Here we set the timeout to a short value to see if GDB will hang in an
# attempt to reconnect with the now closed STDIN. For this test to be
# useful the new temporary timeout MUST be shorter than PIPE_CLOSE_TIMEOUT
# defined in gdb/ser-pipe.c (5 seconds at the time of writing).
set prev_timeout $timeout
set timeout 2
gdb_test "disconnect" ".*" "disconnect and test for hang"
set timeout $prev_timeout
}
save_vars { GDBFLAGS } {
set GDBFLAGS "$GDBFLAGS -ex \"set sysroot\""
# Test with the two remote protocol types.
foreach_with_prefix target { remote extended-remote } {
do_test ${target}
}
}
|
