aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.python
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2021-09-30 19:07:48 +0200
committerTom de Vries <tdevries@suse.de>2021-09-30 19:07:48 +0200
commitdc412de5e954d81dc932be7fa7c2edda992de096 (patch)
treec49756afbe893127cc23065d8cf34b70bc71a219 /gdb/testsuite/gdb.python
parent85d74f293624dec19180d817436818567dc8f9b3 (diff)
downloadbinutils-dc412de5e954d81dc932be7fa7c2edda992de096.zip
binutils-dc412de5e954d81dc932be7fa7c2edda992de096.tar.gz
binutils-dc412de5e954d81dc932be7fa7c2edda992de096.tar.bz2
[gdb/testsuite] Prepare nodebug exec in gdb.base/cvexpr.exp
When running test-case gdb.base/cvexpr.exp with target board unix/-bad, I get: ... gdb compile failed, gcc: error: unrecognized command line option '-bad' ERROR: tcl error sourcing src/gdb/testsuite/gdb.base/cvexpr.exp. ERROR: can't read "use_gdb_stub": no such variable ... This is triggered in a part of the test that claims to require no debug information, but uses the exec containing either dwarf or ctf. Fix this by preparing another executable compiled with nodebug, and using that one instead. Also use with_test_prefix to mark the nodebug part, such that we have: ... gdb compile failed, gcc: error: unrecognized command line option '-bad' UNTESTED: gdb.base/cvexpr.exp: dwarf: failed to prepare gdb compile failed, gcc: error: unrecognized command line option '-bad' UNTESTED: gdb.base/cvexpr.exp: nodebug: failed to prepare ... Tested on x86_64-linux.
Diffstat (limited to 'gdb/testsuite/gdb.python')
0 files changed, 0 insertions, 0 deletions