certi-devel
[Top][All Lists]
Advanced

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

Re: [certi-dev] Time advancement


From: Michael Raab
Subject: Re: [certi-dev] Time advancement
Date: Mon, 22 Nov 2010 13:26:12 +0100

Hi Eric,

log is attached...


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/22/2010 12:52 PM
Betreff:        Re: [certi-dev] Time advancement
Gesendet von:        address@hidden




2010/11/22 Eric Noulard <address@hidden>:
> 2010/11/22 Michael Raab <address@hidden>:
>> Here it is!
>
> Michael,
>
> Your log does not have the trace I would like to know,
> you seem to be using GENDOC (which is ok) but
> I'd rather see the explicit name of ALL Messages
> could you re-run with those var set:
>
> RTIA_MSG=D
> RTIG_MSG=D
>
> Using this we should see the name of each message in the log.

Another patch proposal.
Would you be kind enough to put

throw RTIinternalError(stringize() << "TICK_REQUEST cannot be called
recursively (state=" << static_cast<int>(tm->_tick_state) <<")");

instead of the current
throw RTIinternalError("TICK_REQUEST cannot be called recursively");

That we will see which state we are in before bailing out.
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org

--
CERTI-Devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/certi-devel

Attachment: error_tick1.log
Description: Binary data


reply via email to

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