Bug#509582: still puszed how a non maintainer handled the criticity while not responding to problem

[Eric Valette]

Eric Valette wrote:
> Loïc Minier wrote:
> 
>>  Ok, so if it's only in combination with the experimental libc, or with
>>  an explicit MALLOC_CHECK_=2 export, it's fine to lower the severity a
>>  little; this still is either important or serious.
> 
> Sure.

One more comment: you do not see the *effect* of the bug with
MALLOC_CHECK_=0 but the bug is there and the malloc system may be broken
in unexpected ways. Running valgrind show the bug still happens. Just
the application does not catch it immediately. But who knows what will
happen later.

--eric