[certi-dev] Crash with some STL vector

[Eric Noulard]

2010/11/9 Michael Raab <address@hidden>:
> Hi Eric,
>
> I'm getting an "Debug Assertion Failed!" error, after some execution time.
> ..\include\vector

"some" being, XX minute of elapse time? YY timestep of simulated time ?

> Line: 150
> Expression: ("_Myptr + Off <= ((_Myvec  and so on.
> Seems that a STL vector container in broken.
> At the moment I'm not able to debug into, don't know why, I'll investigate
> this further.

You are probably not able to debug into because the bug appears to be in RTIA
process while you may be debugging the Federate process?
Is that the case?

> The last message I get in RTIA log is: "exit TimeManagement::tick".
> Do you have any idea what may cause such error?
>
> BTW: This was traced using the debug configuration of CERTI. Using release
> our app simply crashes

Is the rtigh still running ?

Using the debug build would be kind enough to setup some env var
inside the federate environment:

RTI_EXCEPTION=X  --> traces RTI exception
CERTI_EXCEPTION=X --> traces CERTI "internal" exception (some of them
are 'normal')

Those two may be setup in rtig context too.

RTIA_TM=Z     --> traces activities of TimeManagement
RTIA_MSG=D -->  traces Federate<-->RTIA message dialog
RTIG_MSG=D --> traces RTIA<-->RTIG message dialog

last one may be setup in rtig context too.

beware that this can lead to a massive slowdown of the simulation because
a great amount of log spitted out.

Using XXXX_MSG on federate side and RTIG side you can trace which was the
last "networked" RTI request, which may gives you more information on where
the issue is.

I may not be as responsive as yesterday this afternoon.

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