--preload and --library-path ?

--preload and --library-path ?

[John Mudd]

[-- Attachment #1: Type: text/plain, Size: 148 bytes --]

Where can I get more info on these options?


1.1.1 release notes

new features:
- new options --preload and --library-path to dynamic linker

John

[-- Attachment #2: Type: text/html, Size: 277 bytes --]

Re: --preload and --library-path ?

[Szabolcs Nagy]

* John Mudd <johnbmudd@gmail.com> [2015-04-01 10:59:22 -0400]:
> Where can I get more info on these options?
> 
> 
> 1.1.1 release notes
> 
> new features:
> - new options --preload and --library-path to dynamic linker
> 

http://git.musl-libc.org/cgit/musl/commit/?id=de45164effdddf500756e10e8c6f56b79301d82b

they do the same as the env vars, just higher precedence
(see ld.so manual for LD_PRELOAD and LD_LIBRARY_PATH)

Re: --preload and --library-path ?

[u-wsnj]

On Wed, Apr 01, 2015 at 10:59:22AM -0400, John Mudd wrote:
> Where can I get more info on these options?
> 
> 1.1.1 release notes
> 
> new features:
> - new options --preload and --library-path to dynamic linker

These are a straightforward and proper (safe) equivalent of the
traditional poorly designed / unsafe LD_PRELOAD and LD_LIBRARY_PATH
environment variables. The options take the arguments with values
corresponding to the ones would-be-put into the variables.
The first non-option argument to the dynamic loader is the binary to be
run, the rest is passed as arguments to the started program.

In contrast to the variables these options are not automatically inherited
by possible child processes and exhibit the correct and safe behaviour.
The variables are atill respected if the corresponding option is not present.

Rune