[vtk-developers] Massive valgrind defects after recent merge

[Andy Bauer]

I saw that but it does:
vtkMapper::vtkMapper()
: ArrayName(NULL)

so it should be fine.

On Thu, Dec 15, 2016 at 10:54 AM, Bill Lorensen <bill.lorensen at gmail.com>
wrote:

> Don't use SetArrayName in the constructor. Use
> this->ArrayName = NULL;
>
> Otherwise it will generate a Undefined Memory Read.
>
>
> On Thu, Dec 15, 2016 at 10:52 AM, Andy Bauer <andy.bauer at kitware.com>
> wrote:
> > It looks like many of them are in vtkMapper::SetArrayName(). I think it's
> > just missing a SetArrayName(NULL) in the destructor. I'll change that as
> my
> > good coding deed of the day :)
> >
> > On Thu, Dec 15, 2016 at 10:27 AM, Bill Lorensen <bill.lorensen at gmail.com
> >
> > wrote:
> >>
> >> Folks,
> >>
> >> Recent changes have resulted in over 5500 valgrind defects.
> >>
> >> Needs attention.
> >>
> >> 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
> >>
> >> Search the list archives at: http://markmail.org/search/?q=
> vtk-developers
> >>
> >> Follow this link to subscribe/unsubscribe:
> >> http://public.kitware.com/mailman/listinfo/vtk-developers
> >>
> >
>
>
>
> --
> Unpaid intern in BillsBasement at noware dot com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20161215/ecd58d9c/attachment.html>