At my wit's end...

New Message Reply Date view Thread view Subject view Author view

Amaury Aubel (aubel++at++lig.di.epfl.ch)
Wed, 16 Jul 1997 16:07:04 -0600


Hi Performers,

I have been trying for days to figure out what is wrong in my pf app. To no
avail. As I said in a previous post my app. crashes or corrupts memory when it
tries to allocate a block of memory from the shared arena:

index = (ushort *)pfMalloc(n*sizeof(ushort),pfGetSharedArena()); (*)
(n is reasonably small)

I suspected a possible memory leak occuring prior to this allocation. I used
Purify (wich btw only works on our Onyx and not on Indigos, Impacts etc. as
Anita rightly pointed out)

I got the following error:
      ZPW: Zero page write
      This is occurring while in:
            _lmalloc [amalloc.c:720]
            _amalloc [amalloc.c:76]
            pfMemory::operator new(unsigned int,unsigned int,void*)
[pfMemory.C:94]
            pfMemory::malloc(unsigned int,void*) [pfMemory.C:369]
            pfMalloc [cMemory.C:30]
            ComputeIndex [Private_libpfRTD.c:534]
      Writing 4 bytes to 0x40

and of course line 534 refers to the line I wrote above and marked with a (*).

The interesting point is that when I redirected the amalloc,afree,arealloc
functions to call their Unix counterparts, thus allocating everything from the
heap and forced the execution in PFMP_APPCULLDRAW mode, the problem vanished!

I would appreciate any hint on this shared memory problem,

Amaury.

=======================================================================
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:37 PDT

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