[gdb/testsuite] Compile dwzbuildid-mismatch more quietly
authorTom de Vries <tdevries@suse.de>
Fri, 24 Apr 2020 11:59:42 +0000 (13:59 +0200)
committerTom de Vries <tdevries@suse.de>
Fri, 24 Apr 2020 11:59:42 +0000 (13:59 +0200)
commit884287754e8da49581b4873b936d8eba7b1f052e
tree5b95028a98e65bce0b6229ea21d7c8b7af382a09
parent4e86f6e7478e40a288ec6567fa7f3b4ef0f8d516
[gdb/testsuite] Compile dwzbuildid-mismatch more quietly

When running test-case gdb.dwarf2/dwzbuildid.exp with target board
cc-with-gdb-index, we have:
...
Running src/gdb/testsuite/gdb.dwarf2/dwzbuildid.exp ...
gdb compile failed, warning: File "dwzbuildid5.o" has a different \
  build-id, file skipped
could not find '.gnu_debugaltlink' file for dwzbuildid-mismatch
warning: File "dwzbuildid5.o" has a different build-id, file skipped
Error while writing index for `dwzbuildid-mismatch': could not find \
  '.gnu_debugaltlink' file for dwzbuildid-mismatch
...
and likewise for target board cc-with-debug-names.

These are gdb-add-index warnings and errors due to the executable
dwzbuildid-mismatch having a build-id mismatch.

Be less verbose by adding "quiet" to the compile flags.

Tested on x86_64-linux.

gdb/testsuite/ChangeLog:

2020-04-24  Tom de Vries  <tdevries@suse.de>

* gdb.dwarf2/dwzbuildid.exp: Add quiet to dwzbuildid-mismatch compile
flags.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.dwarf2/dwzbuildid.exp
This page took 0.027212 seconds and 4 git commands to generate.