diff options
| author | Simon Marchi <simon.marchi@polymtl.ca> | 2022-11-21 09:30:55 -0500 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@efficios.com> | 2022-11-29 11:43:54 -0500 |
| commit | f432d5ef2b955b2f8f1f7c1de727b9e43b846976 (patch) | |
| tree | 694613379ada9bf67374265fa6f741d2e92bc0b4 /gdbsupport/array-view.h | |
| parent | d56614a9925791b15d7052eb4c798ab24a724611 (diff) | |
| download | gdb-f432d5ef2b955b2f8f1f7c1de727b9e43b846976.zip gdb-f432d5ef2b955b2f8f1f7c1de727b9e43b846976.tar.gz gdb-f432d5ef2b955b2f8f1f7c1de727b9e43b846976.tar.bz2 | |
gdb/testsuite: make gdb_unload use gdb_test_multiple
In the failure seen by Philippe here:
https://inbox.sourceware.org/gdb-patches/20221120173024.3647464-1-philippe.waroquiers@skynet.be/
gdb_unload crashed GDB, leaving no trace in the test results. Change it
to use gdb_test_multiple, so that it leaves an UNRESOLVED result. I
think it is good practice anyway.
Make it return the result of gdb_test_multiple directly, change
gdb.python/py-objfile.exp accordingly.
Change gdb.base/endian.exp as well to avoid duplicate test names.
Change gdb.base/gnu-debugdata.exp to avoid recording a test result,
since gdb_unload does it already now.
Change-Id: I59a1e4947691330797e6ce23277942547c437a48
Approved-By: Tom de Vries <tdevries@suse.de>
Diffstat (limited to 'gdbsupport/array-view.h')
0 files changed, 0 insertions, 0 deletions