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

[Thomas W. <tho...@gm...>]

Am Freitag, den 30.05.2008, 08:29 -0500 schrieb Jordi Gutiérrez Hermoso:
> On 30/05/2008, Thomas Weber <tho...@gm...> wrote:
> > I looked into this and I think vtkIdType being int is actually correct,
> >  unless you set VTK_USE_64BIT_IDS (which seems to be unset by default).
> 
> It may work in some cases, but it didn't even compile against the cvs
> VTK. The politically correct action would be to set it to IdType in
> the parser and to let VTK itself decide if that should be an int or
> not. My suspicion is still that the Octaviz parser is producing code
> that is working most of the time but that some obscure undocumented
> feature or bug of the VTK shipped with Debian let it slip by during
> compilation.

I don't think th vtkIdType is really the problem. If my gdb skills are
sufficient[1], then InsertUniquePoint() is called from vtkTriangle with
a vector x of three elements, all of which are NaN.

I don't think that should happen. 

[1] They are quite limited.


> This involves making quite a few modifications to the Octaviz parser,
> in order to make it work with later versions of the VTK bison and flex
> grammar files. I haven't worked on this for the past couple of weeks,
> and the next few weeks involve preparing finals for my students and
> lots of bureaucracy. I still plan, however, to dust off my
> undergraduate notes on parsers and context free grammars and see how I
> can synch Octaviz's parser with the better 64-bit aware grammar. ;-)

Eh, I know basically no C++ and have zero knowledge about parsers and
lexers. Be my guest :)

	Thomas