On 11/06/2015 08:21 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> Make valgrind happy with the current state of the tests, so that
>> it is easier to see if future patches introduce new memory problems
>> without being drowned in noise. Many of the leaks were due to
>> calling a second
Eric Blake writes:
> Make valgrind happy with the current state of the tests, so that
> it is easier to see if future patches introduce new memory problems
> without being drowned in noise. Many of the leaks were due to
> calling a second init without tearing down the data from an earlier
> visi
