Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 28 May 2018 18:16:50 -0400
From: Rich Felker <>
Subject: Re: dl_iterate_phdr() behaves differently on musl and glibc

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


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.