If I change the it.Value() and it2.Value() to it.Get() and it2.Get(), the defect goes away. Value() returns a reference. I suspect that the new comparisons are somehow accessing too much memory.
I'll put a patch in with the replacement. Bill On Mon, Nov 30, 2015 at 12:31 PM, Bill Lorensen <bill.loren...@gmail.com> wrote: > Folks, > > This gerrit commit in August > http://review.source.kitware.com/#/c/20081/ > > is causing this valgrind defect: > https://open.cdash.org/viewDynamicAnalysisFile.php?id=3624555 > > Related to the NotAlmostEquals access. If that is replaced with == the > defect gpoes away, but the test fails. > > If I understood how those new functions work, I might have been able > to give a solution. > > Bill -- Unpaid intern in BillsBasement at noware dot com _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Kitware offers ITK Training Courses, for more information visit: http://kitware.com/products/protraining.php Please keep messages on-topic and check the ITK FAQ at: http://www.itk.org/Wiki/ITK_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/insight-developers
