gdb/testsuite: use a more unique name in gdb.mi/mi-breakpoint-multiple-locations.exp
authorSimon Marchi <simon.marchi@polymtl.ca>
Mon, 7 Nov 2022 14:38:12 +0000 (09:38 -0500)
committerSimon Marchi <simon.marchi@polymtl.ca>
Mon, 7 Nov 2022 15:48:18 +0000 (10:48 -0500)
commit240e07bd94a8da9270c57cde394f6883e43b8497
tree288a28b903e4fa5f908e0fa8070208c3ee01a43a
parentb7096df235486ce718c2a0bfda8a0db074dcb671
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
gdb/testsuite/gdb.mi/mi-breakpoint-multiple-locations.cc
gdb/testsuite/gdb.mi/mi-breakpoint-multiple-locations.exp