| commit | d2fefdedd3a65eaf22d8546835c225c3661e23d8 | |
| author | Alex Bennée <alex.bennee@linaro.org> | |
| Thu, 30 Apr 2020 19:01:16 +0000 (30 20:01 +0100) | ||
| committer | Alex Bennée <alex.bennee@linaro.org> | |
| Wed, 6 May 2020 08:29:26 +0000 (6 09:29 +0100) | ||
| tree | bf13a26e6864b4944b29ccf37fbe47e5fc56fea2 | treesnapshot (tar.gz zip) |
| parent | 38c1c09839c90317314be48f8758e9001ee40b91 | commitdiff |
tests/tcg: better trap gdb failures
It seems older and non-multiarach aware GDBs might not fail gracefully
when faced with something they don't know. For example when faced with
a target XML for s390x the Ubuntu 18.04 gdb will generate an internal
fault and prompt for a core dump.
Work around this by invoking GDB in a more batch orientated way and
then trying to filter out between test failures and gdb failures.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20200430190122.4592-4-alex.bennee@linaro.org>
It seems older and non-multiarach aware GDBs might not fail gracefully
when faced with something they don't know. For example when faced with
a target XML for s390x the Ubuntu 18.04 gdb will generate an internal
fault and prompt for a core dump.
Work around this by invoking GDB in a more batch orientated way and
then trying to filter out between test failures and gdb failures.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20200430190122.4592-4-alex.bennee@linaro.org>
| tests/guest-debug/run-test.py | diffblobblamehistory | |
| tests/tcg/aarch64/gdbstub/test-sve-ioctl.py | diffblobblamehistory | |
| tests/tcg/aarch64/gdbstub/test-sve.py | diffblobblamehistory |