aboutsummaryrefslogtreecommitdiff
path: root/gdb/nat
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2020-04-24 13:59:42 +0200
committerTom de Vries <tdevries@suse.de>2020-04-24 13:59:42 +0200
commit884287754e8da49581b4873b936d8eba7b1f052e (patch)
tree5b95028a98e65bce0b6229ea21d7c8b7af382a09 /gdb/nat
parent4e86f6e7478e40a288ec6567fa7f3b4ef0f8d516 (diff)
downloadgdb-884287754e8da49581b4873b936d8eba7b1f052e.zip
gdb-884287754e8da49581b4873b936d8eba7b1f052e.tar.gz
gdb-884287754e8da49581b4873b936d8eba7b1f052e.tar.bz2
[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.
Diffstat (limited to 'gdb/nat')
0 files changed, 0 insertions, 0 deletions