Andreas Zieringer wrote:
> Hi Antonio,
> 
>> Hi Andreas,
>>
>>
>>> in the scons build system there exist a "invalid_pointer_check" option 
>>> if you enable this the addRefCP, subRefCP, ... methods are replaced by 
>>> some special macros and with these it is possible to detect a subRefCP 
>>> call on a already destroyed pointer. Actually it will report the exact 
>>> source code line with the invalid subRefCP call as a FATAL error 
>>> message. As usual there er some drawbacks with this option, ok the check 
>>> costs a bit processor time, and if you call addRefCP, subRefCP with the 
>>> OSG namespace like OSG::subRefCP this won't work.
>>> If someone knows a solution how to write a macro that works with a 
>>> namespace ...
>>
>> I recompiled the lib but now I get unresolved link errors for addRefCP
>> and subRefCP. Do I have to include a header or do I have to define 
>> something?
>>
>>    Toni
>>
>> P.S.: Yes I recompiled my whole project, yes I link and include the
>> freshly compiled lib (at least I should :)
> 
> ahh ok you have to add this define OSG_INVALID_PTR_CHECK to your 
> projects compile line. Hmm I should add this define to the created 
> OSGConfigured.h header.

Alright... I got it working now. But it's not an awful lot
more information that I get :-) But there are some strange
thing I see on my console.... I have something like this:

delete blabla; <------------ crash ------- I have a printf refcount here

printf( "delete....\n" );

osgExit();


on my console I get:

delete.....
refcount 1....


So I get the printf which is called inside the destructor AFTER the
"delete....". Ok, you might say, that can happen....  But it should
really be sequential. There should be just on thread....

Any Ideas?

   Toni





-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to