public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] [gdb/testsuite] Compile dwzbuildid-mismatch more quietly Date: Fri, 24 Apr 2020 11:59:45 +0000 (GMT) [thread overview] Message-ID: <20200424115945.C495C38930F1@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=884287754e8da49581b4873b936d8eba7b1f052e commit 884287754e8da49581b4873b936d8eba7b1f052e Author: Tom de Vries <tdevries@suse.de> Date: Fri Apr 24 13:59:42 2020 +0200 [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. Diff: --- gdb/testsuite/ChangeLog | 5 +++++ gdb/testsuite/gdb.dwarf2/dwzbuildid.exp | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 8007f486fbc..b16366fc0e7 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2020-04-24 Tom de Vries <tdevries@suse.de> + + * gdb.dwarf2/dwzbuildid.exp: Add quiet to dwzbuildid-mismatch compile + flags. + 2020-04-24 Tom de Vries <tdevries@suse.de> * gdb.dwarf2/dw2-error.exp: Add quiet to compile flags. diff --git a/gdb/testsuite/gdb.dwarf2/dwzbuildid.exp b/gdb/testsuite/gdb.dwarf2/dwzbuildid.exp index 6eead2bb79f..10ad10ae40e 100644 --- a/gdb/testsuite/gdb.dwarf2/dwzbuildid.exp +++ b/gdb/testsuite/gdb.dwarf2/dwzbuildid.exp @@ -138,7 +138,7 @@ if {[gdb_compile [list ${binfile}1.o ${binfile}2.o] ${binfile}-ok \ } if {[gdb_compile [list ${binfile}1.o ${binfile}4.o] ${binfile}-mismatch \ - executable {}] != ""} { + executable {quiet}] != ""} { return -1 }
reply other threads:[~2020-04-24 11:59 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200424115945.C495C38930F1@sourceware.org \ --to=vries@sourceware.org \ --cc=gdb-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).