diff options
author | Tom de Vries <tdevries@suse.de> | 2021-10-13 11:06:36 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2021-10-13 11:06:36 +0200 |
commit | 36170420e329a8d6229eb89b38d8680cf39f1d53 (patch) | |
tree | 347bd307d99d456054c72aa4759434c64e868275 /gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp | |
parent | 746723ba6c1b36d6ec88de3f772a80a8d2de6e4d (diff) | |
download | binutils-gdb-36170420e329a8d6229eb89b38d8680cf39f1d53.tar.gz |
[gdb/testsuite] Fix test name in gdb.python/python.exp
When running test-case gdb.python/python.exp, we have:
...
PASS: gdb.python/python.exp: starti via gdb.execute, not from tty
PASS: gdb.python/python.exp: starti via interactive input
...
The two tests are instances of the same test, with different values for
starti command argument from_tty, so it's strange that the test names are so
different.
This is due to using a gdb_test nested in a gdb_test_multiple, with the inner
one using a different test name than the outer one. [ That could still make
sense if both produced passes, but that's not the case here. ]
Fix this by using $gdb_test_name, such that we have:
...
PASS: gdb.python/python.exp: starti via gdb.execute, not from tty
PASS: gdb.python/python.exp: starti via gdb.execute, from tty
...
Also make this more readable by using variables.
Tested on x86_64-linux.
Diffstat (limited to 'gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp')
0 files changed, 0 insertions, 0 deletions