[gdb/testsuite] Improve failure mode in gdb.dwarf2/enqueued-cu-base-addr.exp
authorTom de Vries <tdevries@suse.de>
Thu, 10 Aug 2023 13:46:30 +0000 (15:46 +0200)
committerTom de Vries <tdevries@suse.de>
Thu, 10 Aug 2023 13:46:30 +0000 (15:46 +0200)
commit107ab8d45df84b442ce2d79c6dda3a9b3afc80d5
tree475e25e52f9146733b1d5368de5d4938eef2bd44
parent62a21046a98d081b5ac07afd0099dfd06465922c
[gdb/testsuite] Improve failure mode in gdb.dwarf2/enqueued-cu-base-addr.exp

I ran test-case gdb.dwarf2/enqueued-cu-base-addr.exp with target board
cc-with-debug-names, and ran into:
...
FAIL: gdb.dwarf2/enqueued-cu-base-addr.exp: ptype foo (GDB internal error)
FAIL: gdb.dwarf2/enqueued-cu-base-addr.exp: CU addr found
...

The first FAIL is a known issue, PR symtab/29572.

The following FAIL is a consequence of the first FAIL, so require for the
second test that the first test passes.

Tested on x86_64-linux, with target boards unix and cc-with-debug-names.
gdb/testsuite/gdb.dwarf2/enqueued-cu-base-addr.exp