aboutsummaryrefslogtreecommitdiff
path: root/ltversion.m4
diff options
context:
space:
mode:
authorAndrew Burgess <andrew.burgess@embecosm.com>2021-03-08 18:11:10 +0000
committerAndrew Burgess <andrew.burgess@embecosm.com>2021-03-12 12:18:33 +0000
commit8a4efb366fadfc8c7eff2994af863a169fe38401 (patch)
tree04206e7dbab97c956bfbb37294ba00a4cd8f106d /ltversion.m4
parent66bb1dd9cda54130515be30ff01061bf5226544e (diff)
downloadgdb-8a4efb366fadfc8c7eff2994af863a169fe38401.zip
gdb-8a4efb366fadfc8c7eff2994af863a169fe38401.tar.gz
gdb-8a4efb366fadfc8c7eff2994af863a169fe38401.tar.bz2
gdb/testsuite: check the correct Python variable in test
While squashing duplicate test names I spotted what looked like a copy & paste error. During this test a Python variable is created, and then we call the type method on that variable. In one case we create a variable and then call the type method on a variable created for a previous test. I can see no reason why this should be what we want, it doesn't line up with the comments in the test script, so I've updated the test. Note, the expected result doesn't change, just the command issued (the test relates to stripping typedefs). gdb/testsuite/ChangeLog: * gdb.python/lib-types.exp: Update the test to check the correct python variable.
Diffstat (limited to 'ltversion.m4')
0 files changed, 0 insertions, 0 deletions