Re: [info-performer] Segfault in pfCullProgram

Date view Thread view Subject view Author view

From: Ken Sewell (sewell++at++dramail.com)
Date: 05/08/2003 13:10:35


The program is running on a dual AMD system with a Geforce 4 Ti4600 (using
the nvidia 1.0-4363 drivers) and yes I am using cliptexture emulation, but
not my own cull programs.

Ken.

On Thu, 8 May 2003, Radomir Mech wrote:

> Hi Ken,
>
> It's hard to say from he trace what is going on. Most likely you have
> a corrupt cull program, which could potentially beresult of some
> memory corruption caused by something else. Bu first I would like to
> find out why the code is going through the cull program path - are you
> using your own cull programs? Are you using clip-texture emulation?
> Also, what hardware are you running it on?
>
> Regards,
> Radomir
>
> Ken Sewell wrote:
> >
> > I'm running a program that places the camera position inside of a vehicle
> > model. When the near clipping is set to 10 (large enough to exclude the
> > vehicle) the simulation runs fine. When I start to step it down it will
> > get to the point where it draws the edges of the vehicle (nose, tail,
> > wingtips...) but if I lower the near clipping plane any more I get a
> > segfault(i.e. near clip of 5.1 runs, but 5.0 segfaults). According to gdb
> > the segfault occurs in pfCullProgram::runCullProgramGeoSet. I'm not sure
> > what would cause this, so I don't know what to look for. This is the info
> > from gdb:
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 1024 (LWP 1136)]
> > 0x40507206 in pfCullProgram::runCullProgramGeoSet(pfGeoSet*, _pfCullPgInfo*, int) () from /usr/lib/libpf.so.3
> > (gdb) where
> > #0 0x40507206 in pfCullProgram::runCullProgramGeoSet(pfGeoSet*, _pfCullPgInfo*, int) () from /usr/lib/libpf.so.3
> > #1 0x40520036 in _pfCuller::pf_getGSetStateCullPgm(pfGeoSet*, pfBillboard*, int, pfString*) () from /usr/lib/libpf.so.3
> > #2 0x4051f416 in _pfCuller::addCullPgm(pfGeoSet*) () from /usr/lib/libpf.so.3
> > #3 0x404b53d5 in pfGeode::nb_cullProgram(int, int, _pfCullPgInfo*, _pfCuller*) () from /usr/lib/libpf.so.3
> > #4 0x404f4f9e in pfSwitch::nb_cullProgram(int, int, _pfCullPgInfo*, _pfCuller*) () from /usr/lib/libpf.so.3
> > #5 0x404b8e22 in pfGroup::nb_cullProgram(int, int, _pfCullPgInfo*, _pfCuller*) () from /usr/lib/libpf.so.3
> > #6 0x404984ee in pfDoubleSCS::nb_cullProgram(int, int, _pfCullPgInfo*, _pfCuller*) () from /usr/lib/libpf.so.3
> > #7 0x404984ee in pfDoubleSCS::nb_cullProgram(int, int, _pfCullPgInfo*, _pfCuller*) () from /usr/lib/libpf.so.3
> > #8 0x404984ee in pfDoubleSCS::nb_cullProgram(int, int, _pfCullPgInfo*, _pfCuller*) () from /usr/lib/libpf.so.3
> > #9 0x404ee1de in pfSCS::nb_cullProgram(int, int, _pfCullPgInfo*, _pfCuller*) () from /usr/lib/libpf.so.3
> > #10 0x404ee1de in pfSCS::nb_cullProgram(int, int, _pfCullPgInfo*, _pfCuller*) () from /usr/lib/libpf.so.3
> > #11 0x404f0a4e in pfScene::nb_cullProgram(int, int, _pfCullPgInfo*, _pfCuller*)() from /usr/lib/libpf.so.3
> > #12 0x4051ea96 in _pfCuller::nb_cull() () from /usr/lib/libpf.so.3
> > #13 0x4053ec70 in beginDraw(int) () from /usr/lib/libpf.so.3
> > #14 0x4053909c in pfDraw () from /usr/lib/libpf.so.3
> > #15 0x08059eb9 in drawFunc(pfChannel*, void*) (chan=0x43390eb0, data=0x0) at mitl_otw.cc:443
> > #16 0x404797e9 in pfChannel::pf_callDrawFunc() () from /usr/lib/libpf.so.3
> > #17 0x40538f95 in doDraw(pfChannel*, pfPipe*, int*) () from /usr/lib/libpf.so.3
> > #18 0x4053daa6 in appCullDraw(int) () from /usr/lib/libpf.so.3
> > #19 0x40536f3d in pfFrame () from /usr/lib/libpf.so.3
> > #20 0x0805a37e in main (argc=1, argv=0xbffff414) at mitl_otw.cc:633
> > #21 0x4109b4a2 in __libc_start_main () from /lib/libc.so.6
> >
> > I'm running kernel 2.4.20 with Performer 3.0.1
> >
> > Any ideas? Thanks.
> >
> > Ken Sewell Defense Research Associates
> > Project Engineer 3915 Germany Lane, Suite 102
> > 937-431-1644 Beavercreek, Ohio 45431-1608
> > sewell++at++dramail.com
> >
> > -----------------------------------------------------------------------
> > List Archives, Info, FAQ: http://www.sgi.com/software/performer/
> > Open Development Project: http://oss.sgi.com/projects/performer/
> > Submissions: info-performer++at++sgi.com
> > Admin. requests: info-performer-request++at++sgi.com
> > -----------------------------------------------------------------------
> > SGI Developer Conference May 12-14 San Jose Marriott Hotel (CA, USA)
> > http://www.sgi.com/developers/conference
> > -----------------------------------------------------------------------
>


Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Thu May 08 2003 - 13:12:17 PDT

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