[vtk-developers] reproducible bug with vtkExtractVOI and vtkImageShiftScale

Charl P. Botha c.p.botha at its.tudelft.nl
Sun Nov 11 16:52:54 EST 2001

Hi Lisa,

I've rebuilt with a fresh CVS update, and I can still reproduce the problem
with the examples I attached on my original mail about this matter.  So, can
it perhaps be that the vtkExtractVOI fix wasn't checked in?

Thanks for any help,

On Sat, Nov 10, 2001 at 11:24:08AM +0100, Charl P. Botha wrote:
> revision 1.24
> date: 2001/01/22 12:48:07;  author: lawcc;  state: Exp;  lines: +7 -7
> Inputs take images instead of structured points.  Also fixed memory leak.
> That was 22 January.  Was the fix for vtkExtractVOI maybe not checked in?
> Perhaps the fix was on a parent class?
> I'm rebuilding as we speak just to make sure, but my last build was about a
> week ago.
> On Fri, Nov 09, 2001 at 10:37:46PM -0500, Lisa Sobierajski Avila wrote:
> > Try to update your vtkExtractVOI.cxx, rebuild, and run this again. I think 
> > the problem is fixed.  vtkExtractVOI was not setting the output scalar type 
> > so vtkImageShiftScale was traversing the data 4 bytes at a time (regardless 
> > of data type) and crashing when it runs out of data.

charl p. botha      | computer graphics and cad/cam 
http://cpbotha.net/ | http://www.cg.its.tudelft.nl/

More information about the vtk-developers mailing list