gdb/testsuite: make gdb_unload use gdb_test_multiple
authorSimon Marchi <simon.marchi@polymtl.ca>
Mon, 21 Nov 2022 14:30:55 +0000 (09:30 -0500)
committerSimon Marchi <simon.marchi@efficios.com>
Tue, 29 Nov 2022 16:43:54 +0000 (11:43 -0500)
commitf432d5ef2b955b2f8f1f7c1de727b9e43b846976
tree694613379ada9bf67374265fa6f741d2e92bc0b4
parentd56614a9925791b15d7052eb4c798ab24a724611
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>
gdb/testsuite/gdb.base/endian.exp
gdb/testsuite/gdb.base/gnu-debugdata.exp
gdb/testsuite/gdb.python/py-objfile.exp
gdb/testsuite/lib/gdb.exp