[ITK-dev] Lingering Valgrind defect

[Bill Lorensen]

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.lorensen at 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