[vtkusers] vtkExtractVOI + vtkStructuredPointsWriter breakage

[Charl P. Botha]

Here's another segfault-causing script.  This time, the output of 
vtkExtractVOI is sent to a vtkStructuredPointsWriter.  This simple 
operation causes segmentation faults on Linux and Windows.

This time, the segfault is in vtkDataWriter::WriteFieldData() at line 
976.  strlen() is being requested on array->GetName().  array exists, 
but ->GetName() returns 0x0.

It would seem that vtkExtractVOI is not correctly naming its output. 
Even if this is the case, shouldn't subsequent filters be robust to 
arrays not having names?

Any further help would be appreciated.

Thanks,
Charl

-- 
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: extractVoiBreakage2.py
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20040229/95b8de65/attachment.asc>