From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: LD_PRELOAD should treat space and colon as separator
Date: Fri, 11 Jul 2014 00:27:57 -0400 [thread overview]
Message-ID: <20140711042757.GX179@brightrain.aerifal.cx> (raw)
In-Reply-To: <53BD72BE.4080101@barfooze.de>
On Wed, Jul 09, 2014 at 06:50:06PM +0200, John Spencer wrote:
> from reading the code in dynlink.c, load_preload(), it appears as if
> musl's LD_PRELOAD only accepts space as a separator.
>
> according to http://man7.org/linux/man-pages/man8/ld.so.8.html
> GLIBC and probably other dynlinker accept ":" as well:
>
> LD_PRELOAD
> A list of additional, user-specified, ELF shared libraries to
> be loaded before all others. The items of the list can be
> separated by spaces or colons.
>
> --JS
Should be fixed by commit 349381aa8c0fc385e54e1068dd5f2b27af55cd12.
Rich
prev parent reply other threads:[~2014-07-11 4:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 16:50 John Spencer
2014-07-11 4:27 ` Rich Felker [this message]
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=20140711042757.GX179@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).