On 11/04/2015 10:44 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> On 11/04/2015 01:19 AM, Markus Armbruster wrote:
>>> Eric Blake writes:
>>>
Make valgrind happy with the current state of the tests, so that
tests/test-qmp-input-strict.c | 10 ++
tests/test-qmp
Eric Blake writes:
> On 11/04/2015 01:19 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
On 11/04/2015 01:19 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
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
visit. But since teardown is alrea
