On 05/05/2008, Jonathan Stickel <
jjstickel@...> wrote:
> Why do you think Dragan has abandoned the project?
---------- Forwarded message ----------
From: Dragan Tubic <
dragan.tubic.1@...>
Date: 5 May 2008 07:42
Subject: Re: Octaviz segfault
To: Jordi Gutiérrez Hermoso <
jordigh@...>
[snip]
Unfortunately I don't work actively on octaviz anymore.
[snip]
:-(
On 05/05/2008, Jonathan Stickel <
jjstickel@...> wrote:
> Jordi Gutiérrez Hermoso wrote:
>
> > On 05/05/2008, Jonathan Stickel <
jjstickel@...> wrote:
> >
> >
> > > About your specific problem, I do not get a segfault on my system (Mac
> OS X
> > > 10.4, octave-3.0.0, octaviz-0.4.7).
> > >
> > >
> >
> > Same versions here. I'm thinking it may be a 64bit issue. Are you
> > using a 32 bit OS?
> >
> I'm not sure.
Well, how about this. What's the sizeof a pointer for you? On my
system, the following C++ code outputs "8". What does it output on
yours?
#include <iostream>
int main(){
using namespace std;
cout << sizeof(int*) << endl;
}
If it's a problem with 64 bit misalignment of pointers, that would be
a good clue to go bug squashing.
Also, looking a bit more closely at VTK's code, I'm starting to think
that I wouldn't put a segfault beyond them. Manually namespacing all
of their functions instead of using C++ namespaces? #including
obsolete C++ headers? Certainly not the cleanest C++ I've seen. The
problem may well lie within VTK proper, not even Octaviz.
Thanks,
- Jordi G. H.
