Re: Problem with pfTexture LoadFile when forking DBASE

New Message Reply Date view Thread view Subject view Author view

From: phowe++at++csc.com
Date: 07/13/2000 18:43:14

Thanks Benedikt!

We have changed our code to load textures after pfConfig and that has fixed the
bus errors etc.

So just to make sure I have it right, it is OK to create libpr objects like
pfGeoSets
and pfTextures before calling pfConfig(), but in the case of a pfTexture you
must
call loadFile after pfConfig(). Is that Right?

thanks again for your help

Peter

This is from the pfdLoadFile manpage:

     pfdLoadFile builds in-memory data structures from an external
database
     file. ...
     pfdLoadFile may only be called after pfConfig.

Probably the same statement is missing in the pfTexture manpage. You
might not be allowed to load the texture before the pfconfig call. Doing
this will indeed cause the problems you mentioned above.

Internal buffers are allocated from shared memory and stored in static
variables.
When the DBASE process gets forked it inherits there variables. If you
continue to load textures from both the APP and the DBASE process, it
may happen that both processes need bigger buffers. As both processes
beleive that they own these buffers, some double pfFree call occur on
the same piece of memory.

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Thu Jul 13 2000 - 19:16:55 PDT

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