Re: segmentation fault in loader

New Message Reply Date view Thread view Subject view Author view

Robert Wolfe (rwolfe++at++dciem.dnd.ca)
Wed, 28 Oct 1998 17:51:28 -0500


I figured it out. I was trying to do something fundamentally incorrect.
I was trying to allocate libpf objects before pfConfig was called.
Doh!

Robert

Robert Wolfe wrote:
>
> Thanks for the tips Mario.
>
> Using Mario's check below, I have verified that the loader does indeed
> seem to finish loading my model into Performer. In fact, complex.c
> reads and displays the model just fine. Where the program is really
> crashing (segmentation fault) is in assigning the node created by
> pfdLoadFile to the scene graph by calling pfScene->addchild(modelnode).
> This is a simple program that creates a 3D display through a
> rendering class object which wraps calls to Performer. I am trying to
> follow the examples but have the feeling I am doing something
> fundamentally wrong. Ideas?
>
> Robert
>
> Mario Veraart wrote:
> >
> > > I have a simple performer application which attempts to read
> > > a model file then display it. I have successfully read all of
> > > the models with Perfly but my program always produces a segmentation
> > > fault in the loader when attempting to load any of these files.
> > > I believe pfdInitConverter is being called appropriately.
>
> > If you use the example program simple.c or complex.c are you able to
> > load the models and view them. If not them you might have a problem with
> > loading the DSO for the loader.
> > use the following to detect what is being loaded by performer
> >
> > setenv PF_LD_LIBRARY_PATH .
> > setenv PFNFYLEVEL 6
> > <run your program>
> >
> > Mario
> =======================================================================
> List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Wed Oct 28 1998 - 14:51:47 PST

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.