shared memory bug

New Message Reply Date view Thread view Subject view Author view

Philip Nemec (nemec++at++precious.asd.sgi.com)
Tue, 8 Apr 1997 12:30:42 -0700

I have a great idea! Just like there is a debugging check about genlock - put
in a debugging check for allocating shared memory after pfConfig. Can you
*please* put in warnings in all the share memory allocation routines that
checks if pfConfig has been called?

Maybe something along the lines of "pf... called after pfConfig - unreliable
effectiveness esp. on later versions of IRIX."
=======================================================================
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 Mon Aug 10 1998 - 17:55:01 PDT

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