From: Daniel Wilkerson <daniel.wilkerson@gmail.com>
To: musl@lists.openwall.com
Cc: Mark Winterrowd <markwinterrowd4@gmail.com>
Subject: Re: request for help with aux
Date: Mon, 27 Jun 2016 14:33:53 -0700 [thread overview]
Message-ID: <CALzRTRnqJ+oRs=4n=jvJprDTvbaTGiT07BwS50xvWBufQSNQyA@mail.gmail.com> (raw)
In-Reply-To: <20160627210013.GA7422@gordon>
Ah, thank you. From that page:
This function is a nonstandard glibc extension.
And:
The primary consumer of the information in the auxiliary vector is
the dynamic linker ld-linux.so(8). The auxiliary vector is a
convenient and efficient shortcut that allows the kernel to
communicate a certain set of standard information that the dynamic
linker usually or always needs. In some cases, the same information
could be obtained by system calls, but using the auxiliary vector is
cheaper.
It seems therefore that if I am doing static linking that it is safe
to simply provide an empty aux vector?
Daniel
On Mon, Jun 27, 2016 at 2:00 PM, Bobby Bingham <koorogi@koorogi.info> wrote:
> On Mon, Jun 27, 2016 at 01:07:59PM -0700, Daniel Wilkerson wrote:
>> This seems to initalize aux to be all zeros, so it seems that in
>> theory all of the aux values could be optional:
>>
>> size_t i, *auxv, aux[AUX_CNT] = { 0 };
>>
>> What I'm wondering is where to find the semantics of all of the aux
>> names; I could hunt through all of the code, but any high-level
>> suggestions you could provide could help a lot. As a bonus, which
>> ones might not have sensible defaults and are actually non-optional,
>> if any.
>
> The getauxval man page is a good starting point:
> http://man7.org/linux/man-pages/man3/getauxval.3.html
>
> --
> Bobby
next prev parent reply other threads:[~2016-06-27 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 20:07 Daniel Wilkerson
2016-06-27 21:00 ` Bobby Bingham
2016-06-27 21:33 ` Daniel Wilkerson [this message]
2016-06-27 21:49 ` Nathan McSween
2016-06-27 21:58 ` Rich Felker
2016-06-28 0:22 ` Patrick Oppenlander
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='CALzRTRnqJ+oRs=4n=jvJprDTvbaTGiT07BwS50xvWBufQSNQyA@mail.gmail.com' \
--to=daniel.wilkerson@gmail.com \
--cc=markwinterrowd4@gmail.com \
--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).