aboutsummaryrefslogtreecommitdiff
path: root/intl
diff options
context:
space:
mode:
authorJoel Brobecker <brobecker@adacore.com>2018-01-04 02:39:58 -0500
committerJoel Brobecker <brobecker@adacore.com>2018-01-04 03:30:37 -0500
commit344420da6beac1e0b2f7964e7101f8dcdb509b0d (patch)
treefe206e4a5f1e26953393fd3b392751e87189f821 /intl
parent66fc87a0d50d2b91322cc24d17461c07925fa867 (diff)
downloadgdb-344420da6beac1e0b2f7964e7101f8dcdb509b0d.zip
gdb-344420da6beac1e0b2f7964e7101f8dcdb509b0d.tar.gz
gdb-344420da6beac1e0b2f7964e7101f8dcdb509b0d.tar.bz2
Add "complete break ada" test to gdb.ada/complete.exp
This patch adds a new test to demonstrate a regression introduced by: commit b5ec771e60c1a0863e51eb491c85c674097e9e13 Date: Wed Nov 8 14:22:32 2017 +0000 Subject: Introduce lookup_name_info and generalize Ada's FULL/WILD name matching The original purpose of the new test is to exercise the "complete" command with an expression for which a large number of matches are returned and to verify that each match returned is a plausible match. In this particular case, the commit above causes GDB to generate additional matches which should in fact not appear in the list (internally generated symbols, or symbols that should be enclosed between "<...>"). These extraneous entries are easy to spot, because they have uppercase characters, such as: break ada__stringsS break ada__strings__R11s [etc] For now, the new test is KFAIL'ed, to avoid generating a new FAIL while we work on fixing that regression. gdb/testsuite/ChangeLog: PR gdb/22670 * gdb.ada/complete.exp: Add "complete break ada" test. Tested on x86_64-linux with GDB built before and after the patch that caused the regression (b5ec771e60c1a0863e51eb491c85c674097e9e13). The test passes before the regression, and generates a KFAIL after.
Diffstat (limited to 'intl')
0 files changed, 0 insertions, 0 deletions