public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug rust/26121] FAIL: gdb.rust/modules.exp: print ::TWENTY_THREE Date: Sat, 11 Jul 2020 22:14:08 +0000 [thread overview] Message-ID: <bug-26121-4717-JDxj7FeImC@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26121-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26121 --- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0ed35c9ae0434dcda2d5d3e3f0be77fa1f323283 commit 0ed35c9ae0434dcda2d5d3e3f0be77fa1f323283 Author: Daniel Xu <dxu@dxuuu.xyz> Date: Fri Jul 3 20:59:53 2020 -0700 rust: Fix rust modules test I noticed that the modules test was failing. Some choice use of `nm` revealed `TWENTY_THREE` was not in the final binary. Fix by taking a pointer to the global, forcing the linker to keep the symbol in. gdb/testsuite/ChangeLog 2020-07-11 Daniel Xu <dxu@dxuuu.xyz> PR rust/26121 * gdb.rust/modules.rs: Prevent linker from discarding test symbol. Signed-off-by: Daniel Xu <dxu@dxuuu.xyz> -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-07-11 22:14 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-16 13:40 [Bug rust/26121] New: " vries at gcc dot gnu.org 2020-06-29 11:29 ` [Bug rust/26121] " vries at gcc dot gnu.org 2020-07-05 15:40 ` vries at gcc dot gnu.org 2020-07-11 22:14 ` cvs-commit at gcc dot gnu.org [this message] 2020-07-11 22:15 ` tromey at sourceware dot org
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-26121-4717-JDxj7FeImC@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).