public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/31780] New: [gdb/testsuite] object files overwritten in gdb.base/ctxobj.exp Date: Tue, 21 May 2024 15:14:20 +0000 [thread overview] Message-ID: <bug-31780-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31780 Bug ID: 31780 Summary: [gdb/testsuite] object files overwritten in gdb.base/ctxobj.exp Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- I ran test-case gdb.base/ctxobj.exp with the fission target board, and ran into trouble. The problem is that there are two shared libraries, build from the same sources, but with different defines. The compilation of the second shared library overwrites the object files of the first library. AFAIK, this is considered bad testsuite style, because we want to be able to find back all artifacts after running a test-case, but it doesn't affect the running of the test-case. However, in the fission case this also overwrites the .dwo files of the first shared library, effectively throwing away the debug info of the first shared library, which does cause trouble. -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2024-05-21 15:14 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=bug-31780-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).