public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alex.ameen.tx at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/27977] Unexpected behavior when using DT_FILTER Date: Wed, 16 Jun 2021 15:39:39 +0000 [thread overview] Message-ID: <bug-27977-131-X9L0Z5Mia9@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27977-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27977 Alex Ameen <alex.ameen.tx at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alex.ameen.tx at gmail dot com --- Comment #1 from Alex Ameen <alex.ameen.tx at gmail dot com> --- Oddly enough I bumped into this exact issue yesterday with a nearly identical example when I was trying to experiment with filters. The behavior is the same on RHEL 7, and NixOS. I got the same behavior when trying to use alternative linkers ( `ld.gold' and `ld.bfd' ). I confirmed the issue by tracing `LD_DEBUG' outputs and found that the linker essentially treats `DT_FILTER' entries as `DT_NEEDED' entries except that they don't need to be explicitly linked during a build - at runtime they are barely more useful than a symlink with their current implementation. In any case I agree that either this is a mistake in the implementation, or misleading documentation. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-06-16 15:39 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-10 10:16 [Bug dynamic-link/27977] New: " tdiff at yandex dot ru 2021-06-11 10:17 ` [Bug dynamic-link/27977] " tdiff at yandex dot ru 2021-06-16 15:39 ` alex.ameen.tx at gmail dot com [this message] 2021-06-18 15:48 ` fweimer at redhat dot com 2021-06-19 20:28 ` tdiff at yandex dot ru 2021-06-19 20:43 ` alex.ameen.tx at gmail dot com 2021-06-19 20:44 ` alex.ameen.tx at gmail dot com 2021-06-28 9:33 ` fweimer at redhat dot com 2021-06-28 18:37 ` tdiff at yandex dot ru 2023-11-13 10:25 ` sam at gentoo 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-27977-131-X9L0Z5Mia9@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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).