Rob Jenkins (robj++at++quid.csd.sgi.com)
Wed, 27 May 1998 08:29:21 -0700
The platform patches will be very different for all those machines, it would be
worth you making sure you have the latest patch sets for each platform ( esp
the Indigo with the problem ), patchset info can be found off:
http://www.sgi.com/support/
The performer patches for pf 2.0 are described in the pf FAQs ( you'd need 1696
and 1392 for a 6.2 machine ), unless you can upgrade to pf 2.2
> 0 pfSequence::nb_getFrame(int*) const(0x1807c400, 0x0, 0x1badbebe,
> 0x5f854664) ["../../../lib/libpf/pfSequence.C":287, 0x5e9261bc]
> 1 pfGetSeqFrame(0x1807c400, 0x0, 0x1badbebe, 0x5f854664)
> ["../../../lib/libpf/cSequence.C":181, 0x5e937204]
> 2 main(0x2, 0x7fff2f54, 0x1badbebe, 0x5f854664) ["../bnl.c":607,
> 0x40500c]
> 3 __istart() ["crt1tinit.s":13, 0x403a30]
>
The 0x1badbebe is a pattern that Performer uses to highlight bad memory values
of some sort, that doesn't help diagnose the problem much though, if you could
double check patches then boil down to the shortest test case possible if it
fails, then please post that ( and log a support call ).
Cheers
Rob
> B. Andrews
> =======================================================================
> List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
>-- End of excerpt from Ballard Andrews; (4/28/98)
--
________________________________________________________________
Rob Jenkins mailto:robj++at++sgi.com
Silicon Graphics, Mtn View, California, USA
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:57:26 PDT