Re: results of gnulib tests with -fsanitize=address

[Paul Eggert]

Bruno Haible wrote:
> Whereas here, memory leaks don't depend on gcc options, nor on the platform.

I was worried more about something like this: a test for feature X has a subtest 
for feature Y that fails, then the feature-X test calls fclose but fclose 
doesn't free the storage because of the feature-Y failure, so then the test for 
X falsely fails because of the leak. I don't want us to get into the business of 
debugging fclose internals merely when we're trying to test for feature X. This 
is partly why I stopped sanitizing tests last year.

Admittedly I don't have any concrete examples of this right now, but if the 
issue starts cropping up then I suspect I will still favor advising people to 
avoid leak-testing when running "configure", rather than bothering to plug leaks 
in the tests. Leaks are not always bugs.