vtkActorToPF and vtk2.4
Paul John Rajlich
prajlich at ncsa.uiuc.edu
Thu Sep 30 15:02:49 EDT 1999
Hello vtkUsers,
vtkActorToPF (rendering with IRIS Performer) now works properly with
vtk2.4. There was a bug that somehow didn't manifest itself with earlier
versions of vtk. Essentially, it came down to calling the wrong method:
primArray->GetSize();
when it should have been:
primArray->GetNumberOfConnectivityEntries();
The new version of vtkActorToPF is now available from the website:
http://hoback.ncsa.uiuc.edu/~prajlich/vtkActorToPF/
Thanks to Per Ekman, Gordon Erlebacher, and Tushar Udeshi for
discovering this problem. Sorry it took so long for me to take
a look at it.
-Paul
----------------------------------------------------------------------
Paul J. Rajlich - prajlich at ncsa.uiuc.edu
Visualization and Virtual Environments
National Center for Supercomputing Applications
http://brighton.ncsa.uiuc.edu/~prajlich/
----------------------------------------------------------------------
On Mon, 27 Sep 1999, Paul John Rajlich wrote:
>
> Per,
>
> sometime this week I'm going to test vtkActorToPF with vtk 2.4.
> I've used all the vtk versions up to vtk2.3, but haven't tried 2.4
> yet. I've had one other person (Gordon Erlebacher) tell me that he's
> had problems with vtkActorToPF and vtk2.4.
>
> -Paul
>
> ----------------------------------------------------------------------
> Paul J. Rajlich - prajlich at ncsa.uiuc.edu
> Visualization and Virtual Environments
> National Center for Supercomputing Applications
> http://brighton.ncsa.uiuc.edu/~prajlich/
> ----------------------------------------------------------------------
>
> On 27 Sep 1999, Per Ekman wrote:
>
> > Hello,
> >
> > I'm having two problems with vtk 2.4. When trying to debug
> > a 2.4 application with gdb (4.18) on Irix 6.5.4 the following
> > happens :
> >
> > (gdb) run drawset
> > Starting program: /afs/pdc.kth.se/home/p/pek/exjobb/src/vtk/CAVEisvis drawset
> > warning: Signal ? does not exist on this system.
> >
> > After this nothing happens. ^C yields
> >
> > /proc/16732: Interrupted function call.
> > PIOCSTATUS or PIOCWSTOP failed.
> > (gdb) bt
> > #0 __start ()
> > at /xlv55/kudzu-apr12/work/irix/lib/libc/libc_n32_M3/csu/crt1text.s:101
> >
> > This does not happen with vtk 2.2.
> > Also the following code :
> >
> > if (sph == NULL) {
> > sph = vtkSphereSource::New();
> > sph->SetRadius(16);
> > sph->SetCenter(reader->GetOutput()->GetPoint(pId));
> >
> > vtkDataSetMapper *sphM = vtkDataSetMapper::New();
> > sphM->SetInput(sph->GetOutput());
> >
> > vtkActor *sphA = vtkActor::New();
> > sphA->SetMapper(sphM);
> > sphA->GetProperty()->SetColor(1.0f, 1.0f, 1.0f);
> >
> > vtkActorToPFTranslator *sphT = vtkActorToPFTranslator::New();
> > sphT->SetActor(sphA);
> > sphT->Init();
> > pfAddChild((pfGroup *)worldDCS, sphT->GetGeode());
> > }
> > else
> > sph->SetCenter(reader->GetOutput()->GetPoint(pId));
> >
> > works fine with vtk 2.2 but the last line (modifying a already created
> > object) causes a SEGFAULT in 2.4. I'm not really sure if this last
> > error is the fault of vtk since dbx gives
> >
> > Process 17573 (CAVEisvis) stopped on signal SIGSEGV: Segmentation violation (default) at [_lfree:799 +0x8,0xfa988c4]
> > Source (of /xlv52/6.5.4f/work/irix/lib/libc/libc_n32_M4/mp/amalloc.c) not available for Process 17573
> > (dbx) where
> >
> > Thread 0x10000
> > > 0 _lfree(0x64233f40, 0x64000000, 0x0, 0x642340d0, 0x0, 0x0, 0x3f88d564, 0x1) ["/xlv52/6.5.4f/work/irix/lib/libc/libc_n32_M4/mp/amalloc.c":799, 0xfa988c4]
> > 1 _afree(0x642340d1, 0x0, 0x0, 0x0, 0x0, 0x0, 0x3f88d564, 0x1) ["/xlv52/6.5.4f/work/irix/lib/libc/libc_n32_M4/mp/amalloc.c":89, 0xfa97a2c]
> > 2 pfMemory::operator delete(void*)(0x64233f40, 0x64233f30, 0x0, 0x642340d0, 0x0, 0x0, 0x3f88d564, 0x1) ["/pfdata/build/perf2.2.5-build/perf/lib/libpr/pfMemory.C":184, 0x3f0cd988]
> > 3 pfMemory::~pfMemory(void)(0x642340d1, 0x64233f30, 0x0, 0x642340d0, 0x0, 0x0, 0x3f88d564, 0x1) ["/pfdata/build/perf2.2.5-build/perf/lib/libpr/pfMemory.C":276, 0x3f0cda44]
> > 4 pfMemory::destroy(void)(0x642340d1, 0x64233f30, 0x0, 0x642340d0, 0x0, 0x0, 0x3f88d564, 0x1) ["/pfdata/build/perf2.2.5-build/perf/lib/libpr/pfMemory.C":791, 0x3f0ce910]
> > 5 pfMemory::unrefDelete(void)(0x64233f40, 0x64233f30, 0x0, 0x642340d0, 0x0, 0x0, 0x3f88d564, 0x1) ["/pfdata/build/perf2.2.5-build/perf/lib/libpr/pfMemory.C":764, 0x3f0ce794]
> > 6 pfMemory::unrefDelete(void*)(0x0, 0x64233f30, 0x0, 0x642340d0, 0x0, 0x0, 0x3f88d564, 0x1) ["/pfdata/build/perf2.2.5-build/perf/lib/libpr/pfMemory.C":1036, 0x3f0d0290]
> > 7 pfGeoSet::pr_refGSet(int (*)(void*))(0x64233e90, 0x3f0d0200, 0x0, 0x642340d0, 0x0, 0x0, 0x3f88d564, 0x1) ["/pfdata/build/perf2.2.5-build/perf/lib/libpr/pfGeoSet.C":2411, 0x3f09b98c]
> > 8 pfGeoSet::~pfGeoSet(void)(0x64233e90, 0x0, 0x0, 0x642340d0, 0x0, 0x0, 0x3f88d564, 0x1) ["/pfdata/build/perf2.2.5-build/perf/lib/libpr/pfGeoSet.C":105, 0x3f082130]
> > 9 pfObject::destroy(void)(0x64233e90, 0x64233f30, 0x0, 0x642340d0, 0x0, 0x0, 0x3f88d564, 0x1) ["/pfdata/build/perf2.2.5-build/perf/lib/libpr/pfObject.C":282, 0x3f0d0fb8]
> > 10 pfBuffer::pf_destroyMem(pfMemory*)(0x64233e90, 0x64233f30, 0x0, 0x642340d0, 0x0, 0x0, 0x3f88d564, 0x1) ["/pfdata/build/perf2.2.5-build/perf/lib/libpf/pfBuffer.C":1460, 0x3ef30820]
> > 11 ::pfDBase(0x642340d1, 0x64233f30, 0x0, 0x642340d0, 0x0, 0x0, 0x3f88d564, 0x1) ["/pfdata/build/perf2.2.5-build/perf/lib/libpf/pfProcess.C":4954, 0x3f006498]
> > 12 ::pfFrame(0x3f42c418, 0x0, 0xc0a00000, 0x3deab368, 0x0, 0x7fff2f04, 0x3f88d564, 0x1) ["/pfdata/build/perf2.2.5-build/perf/lib/libpf/pfProcess.C":3798, 0x3f0059d4]
> > 13 ::main(argc = 2, argv = 0x7fff2f04) ["/afs/pdc.kth.se/home/p/pek/exjobb/src/vtk/CAVEisvis.cxx":649, 0x100383d4]
> > 14 __start() ["/xlv55/kudzu-apr12/work/irix/lib/libc/libc_n32_M3/csu/crt1text.s":177, 0x10035ae8]
> >
> > ...but since the same code works fine with vtk 2.2 I don't know what
> > to make of it. The compiler used for all code (including gdb) but vtk 2.2 is
> > MIPSpro 7.3.
> >
> > Sincerely
> > Per Ekman
> >
> >
> >
> > -----------------------------------------------------------------------------
> > This is the private VTK discussion list. Please keep messages on-topic.
> > Check the FAQ at: <http://www.automatrix.com/cgi-bin/vtkfaq>
> > To UNSUBSCRIBE, send message body containing "unsubscribe vtkusers" to
> > <majordomo at gsao.med.ge.com>. For help, send message body containing
> > "info vtkusers" to the same address. Live long and prosper.
> > -----------------------------------------------------------------------------
> >
>
>
-----------------------------------------------------------------------------
This is the private VTK discussion list. Please keep messages on-topic.
Check the FAQ at: <http://www.automatrix.com/cgi-bin/vtkfaq>
To UNSUBSCRIBE, send message body containing "unsubscribe vtkusers" to
<majordomo at gsao.med.ge.com>. For help, send message body containing
"info vtkusers" to the same address. Live long and prosper.
-----------------------------------------------------------------------------
More information about the vtkusers
mailing list