public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/30031] gdb ctf tests fail with gold Date: Tue, 24 Jan 2023 15:39:52 +0000 [thread overview] Message-ID: <bug-30031-4717-rWpM1rOvSX@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30031-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30031 --- Comment #3 from Tom Tromey <tromey at sourceware dot org> --- (In reply to Nick Alcock from comment #2) > This is expected: gold (like lld and mold) has no support for linking CTF > yet Aha, good to know, thanks. > Until that's done, the GDB CTF tests really need to pre-arrange the > compilation environment so that they always use the built ld (if built) or > don't run (otherwise). gdb doesn't generally use the in-tree linker for tests, and I think it's pretty common for gdb devs to --disable-{ld,gold}. Instead perhaps the test can be changed to either examine the linker somehow (this is kind of a pain) or maybe to just use gdb_test_multiple, detect the failure mode, and kfail. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-24 15:39 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-22 18:03 [Bug symtab/30031] New: " tromey at sourceware dot org 2023-01-22 18:04 ` [Bug symtab/30031] " tromey at sourceware dot org 2023-01-23 4:50 ` tromey at sourceware dot org 2023-01-23 11:29 ` nick.alcock at oracle dot com 2023-01-24 15:39 ` tromey at sourceware dot org [this message] 2023-01-26 14:06 ` nick.alcock at oracle dot com
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-30031-4717-rWpM1rOvSX@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).