What to do when glibc environment variables or tunables conflict?

Siddhesh Poyarekar siddhesh@gotplt.org
Thu Feb 6 11:43:00 GMT 2020


On 06/02/20 14:49, Andreas Schwab wrote:
> 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.

Ahh, I stand corrected for this.  But in that case it should not get in
the way of LD_AUDIT, should it?

>> 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.

The context of my comment is when LD_DEBUG changes behaviour and
conflicts with other options.

Siddhesh



More information about the Libc-alpha mailing list