aboutsummaryrefslogtreecommitdiff
path: root/gdb/configure.ac
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@polymtl.ca>2022-11-07 09:38:12 -0500
committerSimon Marchi <simon.marchi@polymtl.ca>2022-11-07 10:48:18 -0500
commit240e07bd94a8da9270c57cde394f6883e43b8497 (patch)
tree288a28b903e4fa5f908e0fa8070208c3ee01a43a /gdb/configure.ac
parentb7096df235486ce718c2a0bfda8a0db074dcb671 (diff)
downloadgdb-240e07bd94a8da9270c57cde394f6883e43b8497.zip
gdb-240e07bd94a8da9270c57cde394f6883e43b8497.tar.gz
gdb-240e07bd94a8da9270c57cde394f6883e43b8497.tar.bz2
gdb/testsuite: use a more unique name in gdb.mi/mi-breakpoint-multiple-locations.exp
I see failures in this test, due to the function name "add" being too generic, and unexpected breakpoint locations being found in my libstdc++, such as (wrapped for readability): { number="2.4",enabled="y",addr="0x00007ffff7d67e68", func="(anonymous namespace)::fast_float::bigint::add", file="/usr/src/debug/gcc/libstdc++-v3/src/c++17/fast_float/fast_float.h", fullname="/usr/src/debug/gcc/libstdc++-v3/src/c++17/fast_float/fast_float.h", line="1815", thread-groups=["i1"] } Change the test to use a more unique name. Change-Id: I91de781be62d246eb41c73eaa410ebdd12633d1d
Diffstat (limited to 'gdb/configure.ac')
0 files changed, 0 insertions, 0 deletions