From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] elf: Always set l in _dl_init_paths (Bug 23462).
Date: Fri, 25 Oct 2019 12:55:00 -0000 [thread overview]
Message-ID: <6ff07e30-477f-81dd-1948-0900fa9d70c9@redhat.com> (raw)
In-Reply-To: <87tv7x8bme.fsf@oldenburg2.str.redhat.com>
On 10/25/19 4:36 AM, Florian Weimer wrote:
> * Carlos O'Donell:
>
>> This does not turn out to be true. And it makes sense when I think
>> about it more thoroughly.
>>
>> The static executable, lacking a .dynamic section, does not fill in
>> any of the link maps's l_info data, in fact it's all just a list of
>> NULLs because there was no data to load.
>
> Statically linked executables can have dynamic segments. However, there
> seems to be a bug in BFD ld because it ignores -rpath for them.
OK, so we assume you can assemble a minimum .dynamic in a static
executable with a DT_RUNPATH or DT_RPATH that will impact a dlopen
made from a static executable?
Did you file a binutils bug for this?
>> You would have to assemble a static binary with a .dynamic section
>> and the static linker doesn't want to do that.
>
> You can use -static-pie on some targets, then there is a dynamic
> segment, and BFD ld adds DT_RPATH to it.
Oh! That's a great idea, let me add a test case conditioned on that
then, since we have all those pieces in place.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-10-25 12:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 0:01 Carlos O'Donell
2019-10-15 16:24 ` Carlos O'Donell
2019-10-16 9:54 ` Florian Weimer
2019-10-16 11:15 ` Carlos O'Donell
2019-10-16 11:23 ` Florian Weimer
2019-10-16 13:31 ` Carlos O'Donell
2019-10-25 1:16 ` Carlos O'Donell
2019-10-25 8:37 ` Florian Weimer
2019-10-25 12:55 ` Carlos O'Donell [this message]
2021-03-05 18:25 [PATCH] elf: Always set l in _dl_init_paths (bug 23462) Florian Weimer
2021-03-08 22:26 ` Carlos O'Donell
2021-03-09 5:39 ` Navin P
2021-03-09 6:05 ` Florian Weimer
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=6ff07e30-477f-81dd-1948-0900fa9d70c9@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).