This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Testing and LD_PRELOAD

From: Carlos O'Donell <carlos at redhat dot com>
To: Joseph Myers <joseph at codesourcery dot com>, libc-alpha at sourceware dot org
Date: Mon, 20 Aug 2018 20:05:51 -0400
Subject: Re: Testing and LD_PRELOAD
References: <alpine.DEB.2.21.1808202157050.646@digraph.polyomino.org.uk>

On 08/20/2018 05:59 PM, Joseph Myers wrote:
> I saw a few unexpected glibc test failures after an upgrade to Ubuntu 
> 18.04, which I traced to LD_PRELOAD being set by default (to 
> libgtk3-nocsd.so.0) in the environment, which doesn't work for some glibc 
> tests.
> 
> Should the testsuite give an obvious error somewhere early for native 
> testing if you have LD_PRELOAD set?

In configure? I think we should error out very early.

We can't disable /etc/ld.so.preload handling since that would invalidate
the testing we're doing ourselves.

Perhaps eventually we enable DJ's test-in-container, really installed tree
testing, for all the tests? DJ did test this by enabling it for all tests,
and it ran relatively well, but the parallelism issues and disk space
consumption need to be sorted out.

So for now I think an error early in configure is best. That way the developer
knows to adjust their system configuration.

-- 
Cheers,
Carlos.

References:
- Testing and LD_PRELOAD
  - From: Joseph Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]