diff options
| author | Tom de Vries <tdevries@suse.de> | 2022-10-12 16:50:16 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2022-10-12 16:50:16 +0200 |
| commit | e2800454ce9d89f9c4587bc20ee7c6cd0122c340 (patch) | |
| tree | 6747974997d3d6652e810ebdef5514be63157cea /gdb/ada-varobj.c | |
| parent | 7fd882d4ad91916fd8a05148117f05ea9f5d756c (diff) | |
| download | gdb-e2800454ce9d89f9c4587bc20ee7c6cd0122c340.zip gdb-e2800454ce9d89f9c4587bc20ee7c6cd0122c340.tar.gz gdb-e2800454ce9d89f9c4587bc20ee7c6cd0122c340.tar.bz2 | |
[gdb/testsuite] Remove unnecessary perror in some test-cases
On openSUSE Tumbleweed I noticed:
...
UNTESTED: gdb.dwarf2/fission-absolute-dwo.exp: fission-absolute-dwo.exp
ERROR: failed to compile fission-absolute-dwo
...
The ERROR is unnecessary, given that an UNTESTED is already emitted.
Furthermore, it could be argued that it is incorrect because it's not a
testsuite error to not be able to compile something, and UNTESTED or
UNSUPPORTED is more appropriate.
Remove the perror call, likewise in fission-relative-dwo.exp.
Tested on x86_64-linux.
Diffstat (limited to 'gdb/ada-varobj.c')
0 files changed, 0 insertions, 0 deletions