Re: shared memory bug

New Message Reply Date view Thread view Subject view Author view

Don Hatch (hatch++at++hell.asd.sgi.com)
Wed, 9 Apr 1997 15:25:08 -0700

On Apr 8, 12:30pm, Philip Nemec wrote:
> Subject: shared memory bug
> 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."

I must be missing something here (maybe the thread that
led up to this?)

You seem to be implying that calling
        pfMalloc(n, pfGetSharedArena())
should cause a warning if called after pfConfig???
This is certainly not true. E.g. in perfly, the scene graph
is created (loaded) after pfConfig().

And what do you mean by "especially on later versions of IRIX"?

Don

-- 
Don Hatch  hatch++at++sgi.com  (415) 933-5150  Silicon Graphics, Inc.
=======================================================================
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:02 PDT

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