public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/25846] Provide method to show loader search directories
Date: Mon, 20 Apr 2020 09:13:06 +0000 [thread overview]
Message-ID: <bug-25846-131-gJJaAV3jDu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25846-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25846
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |security-
CC| |fweimer at redhat dot com
Severity|normal |enhancement
--- Comment #2 from Florian Weimer <fweimer at redhat dot com> ---
Thanks for the patch. I agree that this is a useful feature.
Please note that we generally discuss patches on the mailing list:
https://sourceware.org/mailman/listinfo/libc-alpha
For a contribution of this size, we will need FSF paperwork unfortunately:
https://sourceware.org/glibc/wiki/Contribution%20checklist#FSF_copyright_Assignment
Regarding the change itself, I think the printing has to be added to ld.so
(elf/rtld.c). ldconfig is statically linked, so could get out of sync with the
dynamic loader. There can also be multiple dynamic loaders with different
search paths be installed on the same system.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-04-20 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 22:38 [Bug dynamic-link/25846] New: " nicholson at endlessm dot com
2020-04-17 22:38 ` [Bug dynamic-link/25846] " nicholson at endlessm dot com
2020-04-17 22:47 ` ijaffery7 at gmail dot com
2020-04-20 9:13 ` fweimer at redhat dot com [this message]
2020-05-03 20:49 ` nicholson at endlessm dot com
2020-05-04 4:14 ` fw at deneb dot enyo.de
2022-01-27 15:45 ` fweimer at redhat 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-25846-131-gJJaAV3jDu@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: link
Be 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).