Hi,

sorry for interrupting ;)

On 03.10.2012 12:59, Halm, Andreas wrote:
>> Hi Gerrit,
>>
>>>> OpenSG WARNING: OSBRootElement::mapPtrField: FieldHandles invalid,
>>> can
>>>> not set pointer - target fc [528] fieldId [8] file id [475] system
>>>> id [528] OpenSG WARNING: OSBRootElement::mapPtrField: FieldHandles
>>>> invalid, can not set pointer - target fc [539] fieldId [8] file id
>>>> [471] system id [539] OpenSG WARNING: OSBRootElement::mapPtrField:
>>>> FieldHandles invalid, can not set pointer - target fc [542] fieldId
>>>> [8] file id [502] system id [542] OpenSG WARNING:
>>>> OSBRootElement::mapPtrField: FieldHandles invalid, can not set
>>>> pointer
>>>> - target fc [553] fieldId [8] file id [498] system id [553] OpenSG
>>>> WARNING: OSBRootElement::mapPtrField: FieldHandles invalid, can not
>>>> set pointer - target fc [556] fieldId [8] file id [529] system id
>>>> [556] OpenSG WARNING: OSBRootElement::mapPtrField: FieldHandles
>>>> invalid, can not set pointer - target fc [567] fieldId [8] file id
>>>> [525] system id [567] OpenSG WARNING: OSBRootElement::mapPtrField:
>>>> FieldHandles invalid, can not set pointer - target fc [528] fieldId
>>>> [6] file id [475] system id [528] OpenSG WARNING:
>>>> OSBRootElement::mapPtrField: FieldHandles invalid, can not set
>>>> pointer
>>>> - target fc [542] fieldId [6] file id [502] system id [542] OpenSG
>>>> WARNING: OSBRootElement::mapPtrField: FieldHandles invalid, can not
>>>> set pointer - target fc [556] fieldId [6] file id [529] system id
>>>> [556]
>>> can you easily identify which fields are behind 8 and 6 and let me
>>> know what kind of ptr fields have a problem. The fcd field part and
>>> the corresponding getHandleXXXX editHandleXXX function definitions for
>>> the particular fields would be a great help.
>> the problem is that i don't know in which type i have to look for field ids 
>> 6 and
>> 8. i am guessing for weak pointers to a custom nodecore though. digging
>> further ...
> i am quite sure now it is the MFUnrecChildWaypointCorePtr type, which has id 
> 6 in one type and id 8 in another type. it is one of these 
> parent-child-pointer constructs.

The code in OSBRootElement looks like this
FWARNING(("OSBRootElement::mapPtrField: FieldHandles invalid, "
                           "can not set pointer - target fc [%u] fieldId 
[%u] file id [%u] system id [%u]\n",
                           (fc != NULL ? fc->getId() : 0), fieldId, 
*idIt, (idMapIt != idMapEnd ? idMapIt->second : 0)));

It outputs the ID of the target FC, but the type names in addition
would be more instructive to the human reader!

Cheers,
Christoph

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to