Searched hist:"2 c7a6dad4de17c357eb91c723bad860c6512a598" (Results 1 – 2 of 2) sorted by relevance
| /freebsd/usr.bin/ldd/ |
| H A D | Makefile | diff 2c7a6dad4de17c357eb91c723bad860c6512a598 Tue Oct 12 00:35:56 CEST 2021 Konstantin Belousov <kib@FreeBSD.org> ldd: do not use dlopen(RTLD_TRACE) for dso when format is specified
Problem is that rtld cannot reliably access updated environment.
This was made more obvious by bfd4c875a10560aaa2. The application
environment can be in arbitrary state and place, system components
can observe it only during execve(2), or in case of rtld, right after
execve, when environment is still at know location and format.
Instead spawn ld-elf.so.1 in direct exec mode which can correctly read
all inherited updates to the environment.
PR: 259069
Reviewed by: arichardson, jhb
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D32464
|
| H A D | ldd.c | diff 2c7a6dad4de17c357eb91c723bad860c6512a598 Tue Oct 12 00:35:56 CEST 2021 Konstantin Belousov <kib@FreeBSD.org> ldd: do not use dlopen(RTLD_TRACE) for dso when format is specified
Problem is that rtld cannot reliably access updated environment.
This was made more obvious by bfd4c875a10560aaa2. The application
environment can be in arbitrary state and place, system components
can observe it only during execve(2), or in case of rtld, right after
execve, when environment is still at know location and format.
Instead spawn ld-elf.so.1 in direct exec mode which can correctly read
all inherited updates to the environment.
PR: 259069
Reviewed by: arichardson, jhb
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D32464
|