This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: What to do when glibc environment variables or tunables conflict?
- From: Andreas Schwab <schwab at suse dot de>
- To: Siddhesh Poyarekar <siddhesh at gotplt dot org>
- Cc: Carlos O'Donell <carlos at redhat dot com>, libc-alpha <libc-alpha at sourceware dot org>, Szabolcs Nagy <szabolcs dot nagy at arm dot com>, Joseph Myers <joseph at codesourcery dot com>, Florian Weimer <fweimer at redhat dot com>
- Date: Thu, 06 Feb 2020 10:19:13 +0100
- Subject: Re: What to do when glibc environment variables or tunables conflict?
- References: <06dd0f65-3a65-b565-d321-aabccd2e3c4c@redhat.com> <b19320d8-9ad6-d5a1-4121-b5c67902a9e1@gotplt.org>
On Feb 06 2020, Siddhesh Poyarekar wrote:
> On 06/02/20 03:42, Carlos O'Donell wrote:
>> Explicit use of LD_BIND_NOW=1 or LD_DEBUG=unused disables ld audit
>> because both uses set GLRO(dl_lazy) to zero and disable lazy binding
>
> LD_DEBUG doing that is a bug.
I disagree. LD_DEBUG=unused is for probing, and doesn't even run the
object. So auditing doesn't come into play.
> To expand on LD_DEBUG, it should be the lowest priority.
No, it should be highest priority. It's a debugging device, so it needs
to be honored to be useful.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."