Re: [Octaviz-help] More on the Octaviz segfault

[Jonathan S. <jjs...@vc...>]

Jordi Gutiérrez Hermoso wrote:
> Hello, Jonathan and Thomas
> 
> Alright, I think I'm getting an idea of what could be wrong. The
> parser that wraps the VTK classes for Octave needs to be fixed for
> 64bit types.
> 
> The most glaring problem I can see, at least against the cvs version
> of VTK, is that the parser is assuming (in Wrapping/vtkParse.l) that
> vtkIdType is an int, while it looks like in 64bit builds vtkIdType is
> actually typedeffed to a long long int. This produced a compile error
> with the cvs VTK, and my guess is that this error was only caught
> later at runtime with the version of VTK in Debian. I haven't looked
> exactly at this latter version, but if Octaviz is somehow giving int*
> when VTK expects long long*, well, that would definitely be a
> segfault.
> 
> The cvs VTK provides better Wrapping/vtkParse.* files for Flex and
> Bison which have the right 64bit types in them, but using them with
> Octaviz requires modifying Octaviz's Wrapping/vtkWrapOctave.c
> 
> I'll keep working on this...
> 
> - Jordi G. H.
> 
> 

Thank you for your efforts here.  I would prefer that octaviz continues 
to work with the latest official release of VTK.  For awhile octaviz was 
programmed against VTK-cvs, which made it very difficult to make a 
release since VTK was long delayed in releasing 5.0.

Jonathan