How does pfMemory know it is a pfMemory?

New Message Reply Date view Thread view Subject view Author view

Keith Babarovich (keithb++at++wormald.com.au)
Thu, 30 May 1996 10:42:45 +1000 (AEST)

As part of our performer 2.0 application we have a binary file format which
loads in all of our GeoSet attributes arrays into one big chunk of PfMemory
and then all the geosets point into different bits of this chunk of
memory.

The pfGeoSet man pages state that you can use either pfMemory allocated
or statically allocated pointers for vertex arrays, etc, but warns that
statically allocated arrays can cause segmentation violations. Well, we
are getting occasional crashes within pfGroup::checkDelete and I am
wondering if this could be the problem.

So my questions are:

How does performer tell if a pointer is to a pfMemory allocated array, or to
a statically allocated array?

I understand that a pfMemory allocated array has a 4 word header, does it
look for this header before deleteing and if so could I place a 4 word header
before each of my attribute arrays for performer to look at so that it would
know that it wasn't a pfMemory and would not try to free it.

------------------------------------------------------------------------------
Keith Babarovich |Diversion contrary to U.S law is prohibited.This
keithb++at++wormald.com.au |email may not be transfered,transshipped or re-
Wormald Technology |exported on a noncontinuous voyage, or otherwise
Advanced Systems Engineering|be disposed of by any unauthorised person without
Ph: +61 2 981 0611 |proper written approval of my mum. EL792126 +

=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer.html
            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:52:56 PDT

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