[vtk-developers] "vtkCommonCoreTcl-TestEmptyInput" fails due to use-after-free in vtkDataEncoder

[Ben Boeckel]

On Mon, Mar 30, 2015 at 17:32:09 -0400, Sean McBride wrote:
> I debugged it a bit and, long story short, the evidence suggested a
> use-after-free so I enabled MallocScribble (on OS X it writes 0x55 to
> freed memory) and caught it in lldb:

FWIW, same thing with glibc:

    export MALLOC_PERTURB_=100

Any value between 1 and 255 will memset() inside of free() (0 disables).
Causes ~5% overhead or so.

--Ben