aboutsummaryrefslogtreecommitdiff
path: root/gdb/python
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2022-04-03 16:48:09 +0100
committerAndrew Burgess <aburgess@redhat.com>2022-04-03 16:48:09 +0100
commit5187219460cd1ba877c555a67adb283c7a2f0d25 (patch)
tree9d5e2f9075eacb5c38754398beddc34248aedda7 /gdb/python
parent9f793f7beda340d847de19d9343d18400a1e21a3 (diff)
downloadbinutils-5187219460cd1ba877c555a67adb283c7a2f0d25.zip
binutils-5187219460cd1ba877c555a67adb283c7a2f0d25.tar.gz
binutils-5187219460cd1ba877c555a67adb283c7a2f0d25.tar.bz2
gdb/testsuite: resolve some duplicate test names in gdb.base
This commit resolves all the duplicate test names that I see in the script: gdb.base/attach-pie-misread.exp The duplicate names all come from a second call to build_executable_own_libs, so in this commit I've places the second call inside a with_test_prefix block. While I was making this change I've also modified the value being passed as the testname for the second build_executable_own_libs call. Previously we used ${test}, however, I think this was likely a mistake, the 'test' variable is setup for the previous test. I suspect that ${testfile} is a better choice - especially now we have a testname prefix. As the testname is only used (after various calls) from within build_executable_from_specs should the build fail, I don't think this change really makes much difference though. There should be no change in what is tested after this commit.
Diffstat (limited to 'gdb/python')
0 files changed, 0 insertions, 0 deletions