Shared arenas and pfDataPool

New Message Reply Date view Thread view Subject view Author view

From: Aline Normoyle (aline++at++mak.com)
Date: 07/20/2000 12:44:40

Hi,

We're in the process of trying to port a performer application to linux
(Red Hat 6.2, gcc version egcs-1.1.2) using Performer 2.3.1. Throughout
the documentation, I keep seeing that Shared Arenas and pfDataPools are
not functional. I'm not sure what this means exactly, however, since the
calls still exist in the libraries and work most of the time (calls such
as pfGetSharedArena() are even being called in the perfly application).

For example, in our application we are occasionally getting crashes in
pfDataPool::find. Here's the call stack:

#0 0x40883e43 in pfDataPool::find () from /usr/lib/libpr.so
#1 0x408717b7 in pfDPoolFind () from /usr/lib/libpr.so
#2 0x4030d240 in pfuNewEventQ () from /usr/lib/libpfutil_ogl.so
#3 0x8143ac8 in initDataPool () at libpfu_input.c:130
#4 0x8143d6d in pfuInitInput (pw=0x86048a0, mode=2) at libpfu_input.c:252
#5 0x810b3ba in main (argc=4, argv=0xbffff7d4) at main.cxx:502

libpfu_input.c is based on the file input.c from libpfutil and the two
functions, pfuInitInput and initDataPool, are identical to the ones which
came with 2.3.1.

What types of things should we be doing to get around "not supported"
functions? Are there any obvious errors which would result in
pfDataPool::find to crashing?

Any information regarding the current state of these memory functions
would be extremely helpful!

thanks, Aline

***********************************************
* Aline Normoyle
* MaK Technologies Product Group
* (617) 876 - 8085 X 137
* aline++at++mak.com
***********************************************

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Thu Jul 20 2000 - 12:47:00 PDT

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