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

[Sean McBride]

On Mon, 30 Mar 2015 18:05:49 -0400, Ben Boeckel said:

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

The OS X one has similarly low overhead, and as such has been enabled on all my dashboards for ages.

Getting off-topic I guess, but given the low overhead and great benefit, would be nice to have it enabled on the continuous and gitlab bots too... (maybe it is?)

Cheers,

-- 
____________________________________________________________
Sean McBride, B. Eng                 sean at rogue-research.com
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montréal, Québec, Canada