diff options
author | Pedro Alves <palves@redhat.com> | 2017-11-16 18:07:41 +0000 |
---|---|---|
committer | Pedro Alves <palves@redhat.com> | 2017-11-16 18:07:41 +0000 |
commit | ea04e54ca8b935b01155c3d40381d879dd6ba683 (patch) | |
tree | 9752de5669dffa3a89b53a36039f4c6dc2b64aae /gdb/breakpoint.c | |
parent | d723696126beb185dc1f8f3196be7cb29948148d (diff) | |
download | binutils-ea04e54ca8b935b01155c3d40381d879dd6ba683.zip binutils-ea04e54ca8b935b01155c3d40381d879dd6ba683.tar.gz binutils-ea04e54ca8b935b01155c3d40381d879dd6ba683.tar.bz2 |
Fix testing gdb.rust/modules.exp against gdbserver
Currently several tests in gdb.rust/modules.exp fail with
--target_board=native-gdbserver:
Running src/gdb/testsuite/gdb.rust/modules.exp ...
FAIL: gdb.rust/modules.exp: call f3()
FAIL: gdb.rust/modules.exp: call self::f2()
FAIL: gdb.rust/modules.exp: call self::super::f2()
FAIL: gdb.rust/modules.exp: call super::f2()
FAIL: gdb.rust/modules.exp: call self::super::super::f2()
FAIL: gdb.rust/modules.exp: call super::super::f2()
FAIL: gdb.rust/modules.exp: call ::f2()
FAIL: gdb.rust/modules.exp: call extern modules::mod1::f2()
This is because these tests rely on matching inferior output.
However, when testing with gdbserver, inferior output goes to a
separate terminal instead of to gdb's terminal, and so gdb_test won't
cut it, as that is only reading from gdb's pty/gdb_spawn_id:
(gdb) call f3()
(gdb) FAIL: gdb.rust/modules.exp: call f3()
call self::f2()
(gdb) FAIL: gdb.rust/modules.exp: call self::f2()
Fix this by using gdb_test_stdio instead, which handles output coming
out of gdbserver's pty.
Also, skip the tests if the target/board doesn't support inferior I/O
at all.
gdb/ChangeLog:
2017-11-16 Pedro Alves <palves@redhat.com>
* gdb.rust/modules.exp: Skip tests that rely on inferior I/O if
gdb,noinferiorio is set, and use gdb_test_stdio otherwise.
Diffstat (limited to 'gdb/breakpoint.c')
0 files changed, 0 insertions, 0 deletions