Re: [certi-dev] Crash with some STL vector

[Eric Noulard]

2010/11/9 Michael Raab <address@hidden>:
> It is the first PAVU request.

I have tried a "blind fix"
I've just checked in CVS, please update an retry
even if I'm pretty sure this is not the end of the story

There is two Federate->RTI services which may generate RTI-->Federate PAVU

RTI::RTIambassador::requestClassAttributeValueUpdate
or
RTI::RTIambassador::requestObjectAttributeValueUpdate

Do you call either of this API or both?
If only one, which one?
If both could you tell me which one is called first (and seems to
generate the first PAVU)?

Since PAVU is a federate ambassador callback could you give me the content
of the callback you use?
i.e. your overloaded version of:

virtual void provideAttributeValueUpdate(RTI::ObjectHandle, const
RTI::AttributeHandleSet &)
        throw (RTI::ObjectNotKnown, RTI::AttributeNotKnown,
RTI::AttributeNotOwned, RTI::FederateInternalError) { }

Is the signature exactly the same as this one (including possibly
thrown Exception)?


If your problem is still there after my blind fix, could you try to add:

PAVU->show(std::cerr);

just before the offending line in RTIambPrivateRefs..cc

should be between line 837 and 838.

837: M_Provide_Attribute_Value_Update* PAVU =
static_cast<M_Provide_Attribute_Value_Update *>(msg);
838:    std::auto_ptr<RTI::AttributeHandleSet> attributeSet(
839:                            new 
AttributeHandleSetImp(PAVU->getAttributes()));

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org