aboutsummaryrefslogtreecommitdiff
path: root/gdbsupport/common-utils.cc
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2022-11-14 12:12:19 +0100
committerTom de Vries <tdevries@suse.de>2022-11-14 12:12:19 +0100
commit8d45c3a82a0eb5ecfc9049bed5569f9e27e3be8c (patch)
tree0ebb89f7edcb00b370ad52e293500665d003d714 /gdbsupport/common-utils.cc
parentfadfefbf159291a685c9849ebf597c1d4d7f75dc (diff)
downloadbinutils-8d45c3a82a0eb5ecfc9049bed5569f9e27e3be8c.zip
binutils-8d45c3a82a0eb5ecfc9049bed5569f9e27e3be8c.tar.gz
binutils-8d45c3a82a0eb5ecfc9049bed5569f9e27e3be8c.tar.bz2
[gdb/testsuite] Set completions to unlimited in get_set_option_choices
In some test-case I tried to use get_set_option_choices "set architecture" and ran into max-completions: ... set architecture simple^M set architecture tomcat^M set architecture xscale^M set architecture *** List may be truncated, max-completions reached. ***^M (gdb) PASS: gdb.base/foo.exp: complete set architecture ... There's only one test-case using this currently: gdb.base/parse_number.exp, and it locally sets max-completions to unlimited. Fix this by: - factoring out a new proc with_set out of proc with_complaints, and - using it to temporarily set max-completions to unlimited in get_set_option_choice. Tested on x86_64-linux, by running test-cases that excercise get_set_option_choice and with_complaints.
Diffstat (limited to 'gdbsupport/common-utils.cc')
0 files changed, 0 insertions, 0 deletions