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
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
|
# Copyright 2021-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/>.
# This test exercises the gdb-gdb.py helper script that is generated
# into the GDB build directory. This script is intended for use by
# developers to make debugging GDB easier.
load_lib selftest-support.exp
if [target_info exists gdb,noinferiorio] {
verbose "Skipping because of no inferiorio capabilities."
return
}
standard_testfile .cc
if { [build_executable "failed to build" $testfile $srcfile {debug c++}] } {
return -1
}
# Find the helper script in the GDB build directory.
set py_helper_script [file dirname $GDB]/gdb-gdb.py
if { ![file readable $py_helper_script] \
|| [file type $py_helper_script] != "file" } {
untested "failed to find gdb-gdb.py helper script"
return
}
# Start GDB and check that we have python support.
gdb_start
if { [skip_python_tests] } {
untested "skipped gdb-gdb.py tests due to lack of python support"
return
}
gdb_exit
# The main test. This is called by the self-test framework once GDB
# has been started on a copy of itself.
proc test_python_helper {} {
global py_helper_script decimal hex gdb_prompt bkptno_numopt_re
global inferior_spawn_id
# Source the python helper script. This script registers the
# pretty printer for the object file called 'gdb', however, in our
# selftests we rename 'gdb' to 'xgdb', so the pretty printer
# doesn't get registered by default.
#
# So, after sourcing the script we do our own objfile scan and
# register the pretty printer for the objfile called 'xgdb'.
gdb_test_no_output "source $py_helper_script" \
"source gdb-gdb.py helper script"
gdb_test [multi_line_input \
"python" \
"for objfile in gdb.objfiles():" \
" if os.path.basename(objfile.filename) == \"xgdb\":" \
" objfile.pretty_printers.append(type_lookup_function)" \
"end"] ".*" \
"register the type pretty printer"
# Now place breakpoints somewhere useful. These locations can be
# any function that:
#
# (a) is easy to reach by issuing a simple gdb command, and
# (b) is unlikely to be modified very often within gdb, and
# (c) has a parameter that is either a 'struct type *' or a 'struct value *'.
gdb_breakpoint value_print qualified
gdb_breakpoint c_print_type qualified
# Disable all breakpoints until after we have loaded the test
# binary into the inner GDB.
gdb_test_no_output "disable breakpoints"
set outer_prompt_re "\\(outer-gdb\\) $"
# Adjust the prompt on the outer gdb, this just makes things a
# little clearer when trying to unpick which GDB is active.
gdb_test_no_output -prompt $outer_prompt_re "set prompt (outer-gdb) " "set outer gdb prompt"
# Send a command to the outer GDB to continue the inner GDB. The
# stop is being detected from the inner GDB, hence the use of -i
# here.
gdb_test_multiple "continue" "start inner gdb" {
-i "$inferior_spawn_id"
-re "received signal SIGSEGV.* in GC_.*$outer_prompt_re" {
# Some versions of the GC used by Guile cause a SEGV
# during stack probing. Ignore this and carry on.
send_gdb "continue\n"
exp_continue
}
-re "\r\n$gdb_prompt $" {
pass $gdb_test_name
}
}
# Load the test executable into the inner GDB. The output here is
# being read from the inner GDB, hence the use of -i here.
send_inferior "file -readnow $::binfile\n"
gdb_test_multiple "" "loading test binary into inner GDB" {
-i "$inferior_spawn_id"
-re "Reading symbols from.*\r\n$gdb_prompt $" {
pass $gdb_test_name
}
}
# Send Ctrl-C to the inner GDB, this should kick us back to the
# prompt of the outer GDB.
send_inferior "\003"
gdb_test -prompt $outer_prompt_re "" "" "interrupted the inner"
# Now enable all breakpoints within the outer GDB.
gdb_test_no_output -prompt $outer_prompt_re "enable breakpoints"
# We need to resume the inner GDB after interrupting it, this is
# done by sending 'continue'. However, GDB will not redisplay the
# prompt in this case, so we have nothing that we can detect in
# order to know this continue was successful. Still, if this
# didn't work, then later tests should fail.
send_gdb "continue\n"
# Control is back with the inner GDB. Send a command to the inner
# GDB, this should result in the outer GDB stopping at one of the
# breakpoints we created..
send_inferior "print 1\n"
gdb_test -prompt $outer_prompt_re "" "Breakpoint $decimal, value_print.*" "hit breakpoint in outer gdb"
# Now inspect the type of parameter VAL, this should trigger the
# pretty printers.
set answer [multi_line \
"${decimal} = " \
"{pointer_type = 0x0," \
" reference_type = 0x0," \
" chain = 0x0," \
" instance_flags = 0," \
" length = $decimal," \
" main_type = $hex}"]
gdb_test -prompt $outer_prompt_re "print *val->type" $answer "pretty print type"
set answer [multi_line \
"$decimal = " \
"{name = $hex \"int\"," \
" code = TYPE_CODE_INT," \
" flags = \[^\r\n\]+," \
" owner = $hex \\(gdbarch\\)," \
" target_type = 0x0," \
" type_specific_field = TYPE_SPECIFIC_NONE}"]
gdb_test -prompt $outer_prompt_re "print *val->type->main_type" $answer "pretty print type->main_type"
# Send the continue to the outer GDB, which resumes the inner GDB,
# we then detect the prompt from the inner GDB, hence the use of
# -i here.
gdb_test_multiple "continue" "resume inner gdb" {
-i $inferior_spawn_id
-re "\r\n$gdb_prompt $" {
pass $gdb_test_name
}
}
# Now print an integer that was created from the DWARF
# information, this will include the TYPE_SPECIFIC_INT
# information.
send_inferior "print global_c.m_val\n"
gdb_test -prompt $outer_prompt_re "" "Breakpoint $decimal, value_print.*" "print integer from DWARF info"
set answer [multi_line \
"$decimal = " \
"{name = $hex \"int\"," \
" code = TYPE_CODE_INT," \
" flags = \[^\r\n\]+," \
" owner = $hex \\(objfile\\)," \
" target_type = 0x0," \
" int_stuff = { bit_size = $decimal, bit_offset = $decimal }}"]
gdb_test -prompt $outer_prompt_re "print *val->type->main_type" $answer "pretty print type->main_type for DWARF type"
# Send the continue to the outer GDB, which resumes the inner GDB,
# we then detect the prompt from the inner GDB, hence the use of
# -i here.
gdb_test_multiple "continue" "resume inner gdb again" {
-i $inferior_spawn_id
-re "\r\n$gdb_prompt $" {
pass $gdb_test_name
}
}
# Send a command to the inner GDB, this should result in the outer
# GDB stopping at the value_print breakpoint again.
send_inferior "ptype global_c\n"
gdb_test -prompt $outer_prompt_re "" "Breakpoint $bkptno_numopt_re, c_print_type.*" "hit breakpoint in outer gdb again"
set answer [multi_line \
"$decimal = " \
"{name = $hex \"CC\"," \
" code = TYPE_CODE_STRUCT," \
" flags = \[^\r\n\]+," \
" owner = $hex \\(objfile\\)," \
" target_type = 0x0," \
" flds_bnds\\.fields\\\[0\\\]:" \
" {m_name = $hex \"m_val\"," \
" m_type = $hex," \
" m_loc_kind = FIELD_LOC_KIND_BITPOS," \
" bitsize = 0," \
" bitpos = 0}," \
" cplus_stuff = $hex}"]
gdb_test -prompt $outer_prompt_re "print *type->main_type" $answer
return 0
}
# Use the self-test framework to run the test.
do_self_tests captured_main test_python_helper
|
