aboutsummaryrefslogtreecommitdiff
path: root/gdb/python
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2021-09-13 09:16:13 +0200
committerTom de Vries <tdevries@suse.de>2021-09-13 09:16:13 +0200
commit003fa0df36e228405bb67069a119408787d7f8c9 (patch)
treef251e0406143413bb0901d77c6b9ca5d81d6bb4c /gdb/python
parent52e5dceb692eec135e27b330d8a6a2d561d11472 (diff)
downloadgdb-003fa0df36e228405bb67069a119408787d7f8c9.zip
gdb-003fa0df36e228405bb67069a119408787d7f8c9.tar.gz
gdb-003fa0df36e228405bb67069a119408787d7f8c9.tar.bz2
[gdb/testsuite] Fix test name in gdb.base/batch-exit-status.exp
When running gdb.base/batch-exit-status.exp I noticed that the test name contains a newline: ... PASS: gdb.base/batch-exit-status.exp: : No such file or directory\.^M : No such file or directory\.: [lindex $result 2] == 0 ... The mistake is that I passed an output regexp argument to a parameter interpreted as testname prefix. Fix this by passing a testname prefix instead. Add support for checking output, to be able to handle the output regexp argument. Tested on x86_64-linux.
Diffstat (limited to 'gdb/python')
0 files changed, 0 insertions, 0 deletions