From: Florian Weimer <fweimer@redhat.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: [PATCH v2] dlinfo.3: Document the RTLD_DI_PHDR request
Date: Wed, 28 Aug 2024 13:50:23 +0200 [thread overview]
Message-ID: <87h6b4hnnk.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <n7mi3i227tecv4waqwxrcq7cg5ll5mws7iirecgvvlgjyh65bs@xmhcxfhfpufz> (Alejandro Colomar's message of "Wed, 28 Aug 2024 13:45:01 +0200")
* Alejandro Colomar:
> Hi Florian,
>
> On Wed, Aug 28, 2024 at 01:01:56PM GMT, Florian Weimer wrote:
>> First added in glibc 2.36, backported upstream to glibc 2.34,
>> so mention 2.34.1 for the first version.
>>
>> Signed-off-by: Florian Weimer <fweimer@redhat.com>
>>
>> ---
>> v2: Fix commit IDs.
>> man/man3/dlinfo.3 | 15 ++++++++++++++-
>> 1 file changed, 14 insertions(+), 1 deletion(-)
>>
>> diff --git a/man/man3/dlinfo.3 b/man/man3/dlinfo.3
>> index 84b696f8c..8158356bd 100644
>> --- a/man/man3/dlinfo.3
>> +++ b/man/man3/dlinfo.3
>> @@ -194,10 +194,23 @@ If this object does not define a PT_TLS segment,
>> or if the calling thread has not allocated a block for it,
>> NULL is placed in
>> .IR *info .
>> +.TP
>> +.BR RTLD_DI_PHDR " (\fIconst ElfW(Phdr *)\fP, since glibc 2.34.1)"
>> +.\" glibc commit d056c212130280c0a54d9a4f72170ec621b70ce5 (2.36)
>> +.\" glibc commit 28ea43f8d64f0dd1f2de75525157730e1532e600 (2.35.1)
>> +.\" glibc commit 91c2e6c3db44297bf4cb3a2e3c40236c5b6a0b23 (2.34.1)
>> +Obtain the address of this shared object's program header and place it
>> +in
>> +.IR *info .
>> +This
>> +.B dlinfo
>> +call returns the number of program headers in the shared object.
>
> Can that number be 0?
No, there has to be at least one PT_LOAD segment.
Thanks,
Florian
next prev parent reply other threads:[~2024-08-28 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 11:01 [PATCH v2] dlinfo.3: Document the RTLD_DI_PHDR request Florian Weimer
2024-08-28 11:45 ` Alejandro Colomar
2024-08-28 11:50 ` Florian Weimer [this message]
2024-08-28 12:34 ` Alejandro Colomar
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=87h6b4hnnk.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=alx@kernel.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox