I catch my exception inside the federate
ambassador RAV callback function.
That is sufficient for me and has no
influences on CERTI.
Michael
Dipl.-Inf. Michael Raab
Fraunhofer-Institut für Fabrikbetrieb und -automatisierung IFF
Virtuell Interaktives Training
Sandtorstr. 22, 39106 Magdeburg, Germany
Telefon +49 (0) 391/ 40 90 122
Telefax +49 (0) 391/ 40 90 115
address@hidden http://www.iff.fraunhofer.de
oder http://www.vdtc.de
Von:
Eric Noulard <address@hidden>
An:
CERTI development discussions
<address@hidden>
Datum:
11/26/2010 01:33 PM
Betreff:
Re: [certi-dev]
Time advancement
Gesendet von:
address@hidden
2010/11/26 Michael Raab <address@hidden>:
> Hi all,
>
> I think there's no problem with the tick management. Sorry for all
the
> confusion.
> The problem was when RAV was delivered during tick() to our observer
> federate, we produced a very nasty exception, that was unfortunately
catched
> by __tick_kernel(). This caused the library to block.
Good to know :-]
May be we can avoid to catch user raised exception we may not be
supposed to catch?
However, we shouldn't be catching exception beside the RTI::XXXX ones.
Did you find a place were we catch something else
(if yes please tell us where)
or did your code raise RTI::XXX exceptions ?
> Thanks for all your efforts & Best regards,
The best problems are those which disappear after some time :-]
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org