From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: dlinfo
Date: Sat, 29 Jun 2013 12:31:17 -0400 [thread overview]
Message-ID: <20130629163117.GL29800@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAK4o1Wz1Ba13nHpiTAEXbQYWHaJTyeJhD4G99gCcaMULM9TtWw@mail.gmail.com>
On Sat, Jun 29, 2013 at 05:14:16PM +0100, Justin Cormack wrote:
> On 29 Jun 2013 16:54, "Rich Felker" <dalias@aerifal.cx> wrote:
> >
> > On Sat, Jun 29, 2013 at 04:40:17PM +0100, Justin Cormack wrote:
> > > Has anyone got any plans to implement dlinfo?
> >
> > I'm not opposed to it, but not sure how easy it would be.
> > RTLD_DI_LINKMAP looks trivial (just return the argument passed in),
> > but the origin and search information is stuff that's probably not
> > saved with the current dynamic linker implementation.
>
> Linkmap is the only bit I need actually. NetBSD apparently only implements
> that and not the rest, so it is not unprecedented.
As a quick workaround then:
-D'dlinfo(x,y,z)=(*(struct link_map *)(z) = (void *)(x))'
Kidding aside, I wouldn't actually recommend this, since you'd be
encoding implementation internals (the fact that the dso handle is
actually the link_map pointer) into the application, which could badly
break if the implementation is ever changed. I'll just go ahead and
add this limited version of dlinfo; look for it soon and ping me if
you don't see it.
Rich
next prev parent reply other threads:[~2013-06-29 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 15:40 dlinfo Justin Cormack
2013-06-29 15:53 ` dlinfo Rich Felker
2013-06-29 16:14 ` dlinfo Justin Cormack
2013-06-29 16:31 ` Rich Felker [this message]
2013-06-29 16:34 ` dlinfo Justin Cormack
2013-06-29 16:39 ` dlinfo Rich Felker
2013-06-29 16:43 ` dlinfo Justin Cormack
2013-06-29 16:48 ` dlinfo Rich Felker
2013-06-30 9:00 ` dlinfo Justin Cormack
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=20130629163117.GL29800@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--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).