[vtk-developers] Valgrind defects after your recent changes

Bill Lorensen bill.lorensen at gmail.com
Mon Jan 30 14:42:38 EST 2012


Yes, they are memory leaks. If you can't figure the origin by looking
at the valgrind report, then you'll have to run valgrind on your
machine.


On Mon, Jan 30, 2012 at 2:38 PM, Yuanxin Liu <leo.liu at kitware.com> wrote:
> Hi, Bill,
>    Is this a memory leak?  How can I reproduce it with local ctest?
> thanks!
> Leo
>
> On Mon, Jan 30, 2012 at 2:17 PM, Bill Lorensen <bill.lorensen at gmail.com>
> wrote:
>>
>> Yuanxin,
>>
>> The change here:
>> http://www.cdash.org/CDash/viewChanges.php?project=VTK&date=2012-01-26
>>
>> resulted in new valgrind defects here:
>> http://www.cdash.org/CDash/viewDynamicAnalysisFile.php?id=2696715
>>
>> Please check the dashboard the day after you check in new code.
>>
>> Thanks,
>>
>> Bill
>>
>> --
>> Unpaid intern in BillsBasement at noware dot com
>
>



-- 
Unpaid intern in BillsBasement at noware dot com



More information about the vtk-developers mailing list