From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: dl_iterate_phdr() behaves differently on musl and glibc
Date: Mon, 28 May 2018 18:16:50 -0400 [thread overview]
Message-ID: <20180528221650.GJ1392@brightrain.aerifal.cx> (raw)
In-Reply-To: <trinity-c25d9df5-7565-4a6b-80b5-34c909b1bf0d-1527543599724@3c-app-mailcom-bs08>
On Mon, May 28, 2018 at 11:39:59PM +0200, Bob B. wrote:
> > Is there a reason musl's behavior is problematic here? Even without
> > the ambiguity I'd be hesitant to change it since programs may be
> > relying on it.
>
> Looking around I found that it caused confusion with libwhich[0] (a program like `which` for dynamic libraries).
> There's an issue opened[1] about it working differently on musl then it does on other systems.
> But I wonder if it causes any problems...
>
> Looking at the code, it looks like Apple systems do the same thing as musl and they treated it individually by skipping the first program on the report (itself)[2]
Rather than special-casing knowledge of particular systems I think the
code should just be fixed so that it doesn't break if the main program
is included.
> Might be worth checking what other systems do (BSDs especially I think) before making the decision.
>
> A clarification on POSIX should also take place. Is that a too bureaucratic process?
POSIX is not relevant since this interface is not defined by POSIX.
I'm rather surprised Apple has it either since it's pretty
ELF-specific...
Rich
next prev parent reply other threads:[~2018-05-28 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 13:44 Bob B.
2018-05-28 20:02 ` Rich Felker
2018-05-28 21:39 ` Bob B.
2018-05-28 22:16 ` Rich Felker [this message]
2018-05-28 22:31 ` Bob B.
2018-05-28 23:16 ` Jameson Nash
2018-05-30 12:33 ` Bob B.
2018-05-28 22:34 ` Luc Van Oostenryck
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=20180528221650.GJ1392@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).