3199e85fd4d3e8c74595bb09f454a87af22f5870
[deliverable/binutils-gdb.git] / gdb / testsuite / lib / completion-support.exp
1 # Copyright 2017-2019 Free Software Foundation, Inc.
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
16 # This file is part of the gdb testsuite.
17
18 # Any variable or procedure in the namespace whose name starts with
19 # "_" is private to the module. Do not use these.
20
21 namespace eval completion {
22 variable bell_re "\\\x07"
23
24 # List of all quote chars.
25 variable all_quotes_list {"'" "\""}
26
27 # List of all quote chars, including no-quote at all.
28 variable maybe_quoted_list {"" "'" "\""}
29
30 variable keyword_list {"if" "task" "thread"}
31
32 variable explicit_opts_list \
33 {"-function" "-label" "-line" "-qualified" "-source"}
34 }
35
36 # Make a regular expression that matches a TAB completion list.
37
38 proc make_tab_completion_list_re { completion_list } {
39 # readline separates the completion columns that fit on the same
40 # line with whitespace. Since we're testing under "set width
41 # unlimited", all completions will be printed on the same line.
42 # The amount of whitespace depends on the length of the widest
43 # completion. We could compute that here and expect the exact
44 # number of ws characters between each completion match, but to
45 # keep it simple, we accept any number of characters.
46 set ws " +"
47
48 set completion_list_re ""
49 foreach c $completion_list {
50 append completion_list_re [string_to_regexp $c]
51 append completion_list_re $ws
52 }
53 append completion_list_re $ws
54
55 return $completion_list_re
56 }
57
58 # Make a regular expression that matches a "complete" command
59 # completion list. CMD_PREFIX is the command prefix added to each
60 # completion match.
61
62 proc make_cmd_completion_list_re { cmd_prefix completion_list start_quote_char end_quote_char } {
63
64 set completion_list_re ""
65 foreach c $completion_list {
66 # The command prefix is included in all completion matches.
67 append completion_list_re [string_to_regexp $cmd_prefix$start_quote_char$c$end_quote_char]
68 append completion_list_re "\r\n"
69 }
70
71 return $completion_list_re
72 }
73
74 # Clear the input line.
75
76 proc clear_input_line { test } {
77 global gdb_prompt
78
79 send_gdb "\003"
80 gdb_test_multiple "" "$test (clearing input line)" {
81 -re "Quit\r\n$gdb_prompt $" {
82 }
83 }
84 }
85
86 # Test that completing LINE with TAB completes to nothing.
87
88 proc test_gdb_complete_tab_none { line } {
89 set line_re [string_to_regexp $line]
90
91 set test "tab complete \"$line\""
92 send_gdb "$line\t"
93 gdb_test_multiple "" "$test" {
94 -re "^$line_re$completion::bell_re$" {
95 pass "$test"
96 }
97 }
98
99 clear_input_line $test
100 }
101
102 # Test that completing INPUT_LINE with TAB completes to
103 # COMPLETE_LINE_RE. APPEND_CHAR_RE is the character expected to be
104 # appended after EXPECTED_OUTPUT. Normally that's a whitespace, but
105 # in some cases it's some other character, like a colon.
106
107 proc test_gdb_complete_tab_unique { input_line complete_line_re append_char_re } {
108
109 set test "tab complete \"$input_line\""
110 send_gdb "$input_line\t"
111 gdb_test_multiple "" "$test" {
112 -re "^$complete_line_re$append_char_re$" {
113 pass "$test"
114 }
115 }
116
117 clear_input_line $test
118 }
119
120 # Test that completing INPUT_LINE with TAB completes to "INPUT_LINE +
121 # ADD_COMPLETED_LINE" and that it displays the completion matches in
122 # COMPLETION_LIST. If MAX_COMPLETIONS then we expect the completion
123 # to hit the max-completions limit.
124
125 proc test_gdb_complete_tab_multiple { input_line add_completed_line \
126 completion_list {max_completions 0}} {
127 global gdb_prompt
128
129 set input_line_re [string_to_regexp $input_line]
130 set add_completed_line_re [string_to_regexp $add_completed_line]
131
132 set expected_re [make_tab_completion_list_re $completion_list]
133
134 if {$max_completions} {
135 append expected_re "\r\n"
136 append expected_re \
137 "\\*\\*\\* List may be truncated, max-completions reached\\. \\*\\*\\*"
138 }
139
140 set test "tab complete \"$input_line\""
141 send_gdb "$input_line\t"
142 gdb_test_multiple "" "$test (first tab)" {
143 -re "^${input_line_re}${completion::bell_re}$add_completed_line_re$" {
144 send_gdb "\t"
145 # If we auto-completed to an ambiguous prefix, we need an
146 # extra tab to show the matches list.
147 if {$add_completed_line != ""} {
148 send_gdb "\t"
149 set maybe_bell ${completion::bell_re}
150 } else {
151 set maybe_bell ""
152 }
153 gdb_test_multiple "" "$test (second tab)" {
154 -re "^${maybe_bell}\r\n$expected_re\r\n$gdb_prompt " {
155 gdb_test_multiple "" "$test (second tab)" {
156 -re "^$input_line_re$add_completed_line_re$" {
157 pass "$test"
158 }
159 }
160 }
161 }
162 }
163 }
164
165 clear_input_line $test
166 }
167
168 # Test that completing LINE with the complete command completes to
169 # nothing.
170
171 proc test_gdb_complete_cmd_none { line } {
172 gdb_test_no_output "complete $line" "cmd complete \"$line\""
173 }
174
175 # Test that completing LINE with the complete command completes to
176 # COMPLETE_LINE_RE.
177
178 proc test_gdb_complete_cmd_unique { input_line complete_line_re } {
179 global gdb_prompt
180
181 set cmd "complete $input_line"
182 set cmd_re [string_to_regexp $cmd]
183 set test "cmd complete \"$input_line\""
184 gdb_test_multiple $cmd $test {
185 -re "^$cmd_re\r\n$complete_line_re\r\n$gdb_prompt $" {
186 pass $test
187 }
188 }
189 }
190
191 # Test that completing "CMD_PREFIX + COMPLETION_WORD" with the
192 # complete command displays the COMPLETION_LIST completion list. Each
193 # entry in the list should be prefixed by CMD_PREFIX. If
194 # MAX_COMPLETIONS then we expect the completion to hit the
195 # max-completions limit.
196
197 proc test_gdb_complete_cmd_multiple { cmd_prefix completion_word completion_list {start_quote_char ""} {end_quote_char ""} {max_completions 0}} {
198 global gdb_prompt
199
200 set expected_re [make_cmd_completion_list_re $cmd_prefix $completion_list $start_quote_char $end_quote_char]
201
202 if {$max_completions} {
203 append expected_re \
204 "$cmd_prefix \\*\\*\\* List may be truncated, max-completions reached\\. \\*\\*\\*.*\r\n"
205 }
206
207 set cmd_re [string_to_regexp "complete $cmd_prefix$completion_word"]
208 set test "cmd complete \"$cmd_prefix$completion_word\""
209 gdb_test_multiple "complete $cmd_prefix$completion_word" $test {
210 -re "^$cmd_re\r\n$expected_re$gdb_prompt $" {
211 pass $test
212 }
213 }
214 }
215
216 # Test that completing LINE completes to nothing.
217
218 proc test_gdb_complete_none { input_line } {
219 test_gdb_complete_tab_none $input_line
220 test_gdb_complete_cmd_none $input_line
221 }
222
223 # Test that completing INPUT_LINE completes to COMPLETE_LINE_RE.
224 #
225 # APPEND_CHAR is the character expected to be appended after
226 # EXPECTED_OUTPUT when TAB completing. Normally that's a whitespace,
227 # but in some cases it's some other character, like a colon.
228 #
229 # If MAX_COMPLETIONS is true, then we expect the completion to hit the
230 # max-completions limit. Since we're expecting a unique completion
231 # match, this will only be visible in the "complete" command output.
232 # Tab completion will just auto-complete the only match and won't
233 # display a match list.
234 #
235 # Note: usually it's more convenient to pass a literal string instead
236 # of a regular expression (as COMPLETE_LINE_RE). See
237 # test_gdb_complete_unique below.
238
239 proc test_gdb_complete_unique_re { input_line complete_line_re {append_char " "} {max_completions 0}} {
240 set append_char_re [string_to_regexp $append_char]
241 test_gdb_complete_tab_unique $input_line $complete_line_re $append_char_re
242
243 # Trim INPUT_LINE and COMPLETE LINE, for the case we're completing
244 # a command with leading whitespace. Leading command whitespace
245 # is discarded by GDB.
246 set input_line [string trimleft $input_line]
247 set expected_output_re [string trimleft $complete_line_re]
248 if {$append_char_re != " "} {
249 append expected_output_re $append_char_re
250 }
251 if {$max_completions} {
252 set max_completion_reached_msg \
253 "*** List may be truncated, max-completions reached. ***"
254 set input_line_re \
255 [string_to_regexp $input_line]
256 set max_completion_reached_msg_re \
257 [string_to_regexp $max_completion_reached_msg]
258
259 append expected_output_re \
260 "\r\n$input_line_re $max_completion_reached_msg_re"
261 }
262
263 test_gdb_complete_cmd_unique $input_line $expected_output_re
264 }
265
266 # Like TEST_GDB_COMPLETE_UNIQUE_RE, but COMPLETE_LINE is a string, not
267 # a regular expression.
268
269 proc test_gdb_complete_unique { input_line complete_line {append_char " "} {max_completions 0}} {
270 set complete_line_re [string_to_regexp $complete_line]
271 test_gdb_complete_unique_re $input_line $complete_line_re $append_char $max_completions
272 }
273
274 # Test that completing "CMD_PREFIX + COMPLETION_WORD" adds
275 # ADD_COMPLETED_LINE to the input line, and that it displays
276 # COMPLETION_LIST as completion match list. COMPLETION_WORD is the
277 # completion word. If MAX_COMPLETIONS then we expect the completion
278 # to hit the max-completions limit.
279
280 proc test_gdb_complete_multiple {
281 cmd_prefix completion_word add_completed_line completion_list
282 {start_quote_char ""} {end_quote_char ""} {max_completions 0}
283 } {
284 test_gdb_complete_tab_multiple "$cmd_prefix$completion_word" $add_completed_line $completion_list $max_completions
285 test_gdb_complete_cmd_multiple $cmd_prefix $completion_word $completion_list $start_quote_char $end_quote_char $max_completions
286 }
287
288 # Test that all the substring prefixes of INPUT from [0..START) to
289 # [0..END) complete to COMPLETION_RE (a regular expression). If END
290 # is ommitted, default to the length of INPUT.
291
292 proc test_complete_prefix_range_re {input completion_re start {end -1}} {
293 if {$end == -1} {
294 set end [string length $input]
295 }
296
297 for {set i $start} {$i < $end} {incr i} {
298 set line [string range $input 0 $i]
299 test_gdb_complete_unique_re "$line" $completion_re
300 }
301 }
302
303 # Test that all the substring prefixes of COMPLETION from [0..START)
304 # to [0..END) complete to COMPLETION. If END is ommitted, default to
305 # the length of COMPLETION.
306
307 proc test_complete_prefix_range {completion start {end -1}} {
308 set completion_re [string_to_regexp $completion]
309 test_complete_prefix_range_re $completion $completion_re $start $end
310 }
311
312 # Find NEEDLE in HAYSTACK and return the index _after_ NEEDLE. E.g.,
313 # searching for "(" in "foo(int)" returns 4, which would be useful if
314 # you want to find the "(" to try completing "foo(".
315
316 proc index_after {needle haystack} {
317 set start [string first $needle $haystack]
318 if {$start == -1} {
319 error "could not find \"$needle\" in \"$haystack\""
320 }
321 return [expr $start + [string length $needle]]
322 }
323
324 # Create a breakpoint using BREAK_COMMAND, and return the number
325 # of locations found.
326
327 proc completion::_create_bp {break_command} {
328 global gdb_prompt
329 global decimal hex
330
331 set found_locations -1
332
333 set test "set breakpoint"
334 gdb_test_multiple "$break_command" $test {
335 -re "\\\(\($decimal\) locations\\\)\r\n$gdb_prompt $" {
336 set found_locations "$expect_out(1,string)"
337 }
338 -re "Breakpoint $decimal at $hex: file .*, line .*$gdb_prompt $" {
339 set found_locations 1
340 }
341 -re "Make breakpoint pending on future shared library load.*y or .n.. $" {
342 send_gdb "n\n"
343 gdb_test_multiple "" "$test (prompt)" {
344 -re "$gdb_prompt $" {
345 }
346 }
347 set found_locations 0
348 }
349 -re "invalid explicit location argument, \[^\r\n\]*\r\n$gdb_prompt $" {
350 set found_locations 0
351 }
352 -re "Function \[^\r\n\]* not defined in \[^\r\n\]*\r\n$gdb_prompt $" {
353 set found_locations 0
354 }
355 }
356 return $found_locations
357 }
358
359 # Return true if lists A and B have the same elements. Order of
360 # elements does not matter.
361
362 proc completion::_leq {a b} {
363 return [expr {[lsort $a] eq [lsort $b]}]
364 }
365
366 # Check that trying to create a breakpoint using BREAK_COMMAND fails.
367
368 proc check_setting_bp_fails {break_command} {
369 with_test_prefix "\"$break_command\" creates no bp locations" {
370 set found_locations [completion::_create_bp $break_command]
371 gdb_assert {$found_locations == 0} "matches"
372 if {$found_locations != 0} {
373 delete_breakpoints
374 }
375 }
376 }
377
378 # Check that creating the breakpoint using BREAK_COMMAND finds the
379 # same breakpoint locations as completing BREAK_COMMAND.
380 # COMPLETION_LIST is the expected completion match list.
381
382 proc check_bp_locations_match_list {break_command completion_list} {
383 global gdb_prompt
384 global hex
385
386 with_test_prefix "compare \"$break_command\" completion list with bp location list" {
387 set num_locations [completion::_create_bp $break_command]
388
389 set found_list ""
390
391 set any "\[^\r\n\]*"
392
393 gdb_test_multiple "info breakpoint \$bpnum" "info breakpoint" {
394 -re "in \(\[^\r\n\]*\) at " {
395 # A function location.
396 set found_location "$expect_out(1,string)"
397 lappend found_list $found_location
398 exp_continue
399 }
400 -re "breakpoint${any}keep${any}y${any}$hex\[ \t]*\(${any}\)\r\n" {
401 # A label location.
402 set found_location "$expect_out(1,string)"
403 lappend found_list $found_location
404 exp_continue
405 }
406 -re "$gdb_prompt $" {
407 }
408 }
409
410 gdb_assert {[completion::_leq $found_list $completion_list]} "matches"
411
412 delete_breakpoints
413 }
414 }
415
416 # Build linespec and explicit locations out of all the combinations of
417 # SOURCES, FUNCTIONS and LABELS, with all combinations of possible
418 # quoting and whitespace around separators, and run BODY_LINESPEC and
419 # BODY_EXPLICIT in the context of the caller for each combination. A
420 # variable named "location" is set in the callers context with the
421 # currently iterated location.
422
423 proc foreach_location_functions { sources functions body_linespec body_explicit } {
424 upvar source source
425 upvar function function
426 upvar source_sep source_sep
427 upvar location location
428
429 foreach source $sources {
430 # Test with and without source quoting.
431 foreach sqc $completion::maybe_quoted_list {
432 if {$source == "" && $sqc != ""} {
433 # Invalid combination.
434 continue
435 }
436
437 # Test with and without function quoting.
438 foreach fqc $completion::maybe_quoted_list {
439 # Test known and unknown functions.
440 foreach function $functions {
441 # Linespec version. Test with and without spacing
442 # after the source/colon colon separator.
443 foreach source_sep {"" ":" ": "} {
444 # Skip invalid combinations.
445 if {$source == "" && $source_sep != ""} {
446 continue
447 }
448 if {$source != "" && $source_sep == ""} {
449 continue
450 }
451
452 set location "${sqc}${source}${sqc}${source_sep}${fqc}$function${fqc}"
453 uplevel 1 $body_linespec
454 }
455
456 # Explicit locations version.
457 if {$source != ""} {
458 set loc_src "-source ${sqc}${source}${sqc} "
459 } else {
460 set loc_src ""
461 }
462
463 set location "${loc_src}-function ${fqc}$function${fqc}"
464 uplevel 1 $body_explicit
465 }
466 }
467 }
468 }
469 }
470
471 # Same as foreach_locations_functions, but also iterate over
472 # combinations of labels.
473 proc foreach_location_labels { sources functions labels body_linespec body_explicit } {
474 upvar source source
475 upvar function function
476 upvar label label
477 upvar source_sep source_sep
478 upvar label_sep label_sep
479 upvar location location
480
481 # Test both with a known source file and without a source file
482 # component.
483 foreach_location_functions \
484 $sources \
485 $functions \
486 {
487 # Linespec version. Test various spacing around the label
488 # colon separator.
489 set saved_location ${location}
490 foreach label_sep {":" " :" ": " " : "} {
491 # Test both known and unknown label.
492 foreach label $labels {
493 set location "${saved_location}${label_sep}$label"
494 uplevel 1 $body_linespec
495 }
496 }
497 } \
498 {
499 # Explicit locations version.
500 set saved_location ${location}
501 foreach label $labels {
502 set location "${saved_location} -label $label"
503 uplevel 1 $body_explicit
504 }
505 }
506 }
507
508 # Check that completion of INPUT_LINE results in GDB completing on all
509 # command names.
510 proc test_gdb_completion_offers_commands {input_line} {
511 global gdb_prompt
512
513 # There are two many commands to usefully check here. So we force
514 # max-completions to 2, and check if those 2 come out.
515
516 # Save current max-completions.
517 set max_completions 0
518 set test "show max-completions"
519 gdb_test_multiple $test $test {
520 -re "Maximum number of completion candidates is (.*)\\.\r\n$gdb_prompt $" {
521 set max_completions $expect_out(1,string)
522 }
523 }
524
525 # Force showing two commands.
526 gdb_test_no_output "set max-completions 2" ""
527
528 test_gdb_complete_multiple $input_line "" "" {
529 "!"
530 "+"
531 } "" "" 1
532
533 # Restore.
534 gdb_test_no_output "set max-completions $max_completions" ""
535 }
This page took 0.047288 seconds and 3 git commands to generate.