Date: Mon, 5 May 2008 14:00:03 -0500
From: " Jordi Guti?rrez Hermoso " <address@hidden>
Subject: Octaviz segfaults
To: "Octave Maintainers List" <address@hidden>
Message-ID:
<address@hidden>
Content-Type: text/plain; charset="iso-8859-1"
Octaviz segfaults on the attached sample script and data.
I'd simplify the test case, but I've honestly have been unable to
figure out what's so particular about this data to make it segfault.
I've tried other similar approaches without getting a segfault.
Also attached you will find a stack trace.
Now, I know that Octaviz isn't really part of Octave proper, but I
really have no idea where else to ask for help. Dragan Tubic, the
former lead developer of Octaviz, has abandoned Octaviz. :-( It's also
hard to tell, as you can see from the tangled web of a stack trace, to
know if the segfault is Octave's, Octaviz's or VTK's fault. I'm
leaning towards Octaviz, as a segfault in the other two would probably
be noticed by members of their respective communities.
I'm not asking for a complete solution... I'm happy to dig through the
code myself and see what's wrong, and in fact, I've already tried. I
am just asking for a little bit of help. My current guess is that
Octaviz is somehow not keeping a proper reference count (#21 in the
stack trace below looks like a likely candidate to look for problems).
Maybe I'm also asking if it's worthwhile rescuing Octaviz. I do think
that VTK produces some of the prettiest graphics all around, but so
much effort is now spent on other graphics backends for Octave, that
perhaps it's ok to let Octaviz die.
Thanks,
- Jordi G. H.