From: Marc Mendez (mmendez++at++silicon-worlds.fr)
Date: 05/27/2003 07:17:22
pfHi Performers !
I m running Performer 3.0.1/RH8 on SGI 330VW.
I m trying to understand a weird behaviour in my application totally
written in C++.
We have one module that I called overlaytext_module that prints messages
on screen on top of the scene.
That module is able to get a "field" value (which is derived from the
Open Inventor concept) and print it at every frame drawing.
My problem is that the field implements a DATA* _value; member which
causes problems:
- if I declare in the constructor: _value = new DATA; everything goes fine,
- if I declare _value = (DATA*)pfMalloc(sizeof(DATA)); I ***** USUALLY
DON T HAVE THE LAST UPDATE OF MY FIELD'S VALUE", "sometimes" it gets
refreshed ... a behaviour that segfaults my computer applications
developer's brain which makes me tired rebooting again and again 8)
As DATA can be an int32_t, a double, a float ... I was expecting that I
HAD to pfMalloc to share it among the PF processes. This field is
created in the APP process and is read in the Overlay callback of my
module, that is the DRAW process.
Maybe should I stick using stdc++::new operator until it causes me
severe damages ... but I can t understand that a data that should be
shared in the PF arena can t be read, any clues ?
pfRegards,
Marc.
-- Marc Mendez Silicon Worlds SA12, rue de Chatillon 75014 Paris Tel : +33 (01) 53 90 11 13 Fax : +33 (01) 53 90 11 12
Without C, we would only have Basi, Pasal and Obol. Anonymous. Computers are useless. They can only give you answers. P. Picasso.
This archive was generated by hypermail 2b29 : Tue May 27 2003 - 07:18:34 PDT