mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Bob B." <bob66@gmx.com>
To: "Jameson Nash" <vtjnash@gmail.com>
Cc: musl@lists.openwall.com, ararslan@comcast.net, jakub@jirutka.cz
Subject: Re: dl_iterate_phdr() behaves differently on musl and glibc
Date: Wed, 30 May 2018 14:33:07 +0200	[thread overview]
Message-ID: <trinity-cbebf0d0-be04-4d9f-b187-942fd3834c06-1527683587903@3c-app-mailcom-bs03> (raw)
In-Reply-To: <CADnnjUUfK-SaXANRjZeCYYGFS2qH8qbKLEyMs8BJWM+sWQa8sw@mail.gmail.com>

> So seems like the main difference is just that on Ubuntu the first entry doesn't have a name
Yes, I mistakenly thought it wasn't reported for some reason, but they just don't have a name.

> Which seems to suggest that users should just unconditionally skip the first entry if they aren't interested in the program name.
> Does that sound right?
It sounds right. But the question now is what should libwhich do.
Ignore first entry on musl too or start to report first entry on glibc. (first entry being the program itself).
As libwhich is used to determine what are the dependencies of a program I don't think it's really necessary to point out that it depends on itself. But it doesn't do any harm either... And could simplify code (also taking away the special handle for Apple systems).
Either way it should be consistent across systems.
Nice work! Let us know what you choose.


  reply	other threads:[~2018-05-30 12:33 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
2018-05-28 22:31       ` Bob B.
2018-05-28 23:16         ` Jameson Nash
2018-05-30 12:33           ` Bob B. [this message]
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=trinity-cbebf0d0-be04-4d9f-b187-942fd3834c06-1527683587903@3c-app-mailcom-bs03 \
    --to=bob66@gmx.com \
    --cc=ararslan@comcast.net \
    --cc=jakub@jirutka.cz \
    --cc=musl@lists.openwall.com \
    --cc=vtjnash@gmail.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).