certi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [certi-dev] Time advancement


From: Eric Noulard
Subject: Re: [certi-dev] Time advancement
Date: Tue, 16 Nov 2010 16:32:18 +0100

2010/11/16 Michael Raab <address@hidden>:
> As far as I can see I only call tick(0.1f, 0.05f) once every loop in the
> main loop of the observer.
> The only callbacks I handle are:
>
> - receiveInteraction
> - reflectObjectValues
> - removeObjectInstance
> - timeConstrainedEnabled
> - timeRegulationEnabled

The callback does not really matter, what matters is
which libRTI/RTIambassador calls do you do
from **WITHIN** those callbacks.

> Any ideas on how to track that issue down?

1) Look at the code of each callback and examine which call to  libRTI you do.
2) Look where SpecifiedSaveLabelDoesNotExist could be raised.

> Which logging levels would you  propose?

In the Observer federate context:

RTIA_MSG=D
RTI_EXCEPTION=X
CERTI_EXCEPTION=X
and may be
RTIG_MSG=D

You shoud see the interleaving of message which raise the exception.
-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org



reply via email to

[Prev in Thread] Current Thread [Next in Thread]