aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/lib/gdb-python.exp
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2022-06-09 13:40:07 +0100
committerAndrew Burgess <aburgess@redhat.com>2022-06-09 13:40:07 +0100
commitb1054b67df3e06d92c4e11e25eece679859ac683 (patch)
treec122ad6daf6b5365e133b6bda5875cbdf5e8fc3d /gdb/testsuite/lib/gdb-python.exp
parent417d2514ef183c2beacd932651c6684743130ab6 (diff)
downloadgdb-b1054b67df3e06d92c4e11e25eece679859ac683.zip
gdb-b1054b67df3e06d92c4e11e25eece679859ac683.tar.gz
gdb-b1054b67df3e06d92c4e11e25eece679859ac683.tar.bz2
gdb/testsuite: resolve duplicate test names in gdb.threads/tls.exp
While running the gdb.threads/tls.exp test with a GDB configured without Python, I noticed some duplicate test names. This is caused by a call to skip_python_tests that is within a proc that is called multiple times by the test script. Each call to skip_python_tests results in a call to 'unsupported', and this causes the duplicate test names. After this commit we now call skip_python_tests just once and place the result into a variable. Now, instead of calling skip_python_tests multiple times, we just check the variable. There should be no change in what is tested after this commit.
Diffstat (limited to 'gdb/testsuite/lib/gdb-python.exp')
0 files changed, 0 insertions, 0 deletions