Correction! The message is sent out correctly
and is handled in libRTI.
The crash seems to occur in AttributeHandleSetImp
constructor which is called in RTIambPrivateRefs::callFederateAmbassador.
My problem right now is that I cannot
debug in rti_ng.lib. Hope this is enough information for you.
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:
Michael Raab <address@hidden>
An:
CERTI development discussions
<address@hidden>
Datum:
11/09/2010 03:11 PM
Betreff:
Re: [certi-dev]
Crash with some STL vector
Gesendet von:
address@hidden
Hi Eric,
I investigated in more detail and this is what I found out.
The problem is kind of related to a provideAttributeValueUpdate call. I've
attached an overview of the last RTIA function calls in my console.
I set a break point into ObjectManagement::provideAttributeValueUpdate()
function. The break point is so far only reached once. Good. :-)
If I step through, the actual assert is thrown in SocketUN::send() in line
231.
Ideas? Do you need more information?
Best regards,
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/09/2010
02:03 PM
Betreff: [certi-dev]
Crash with some STL vector
Gesendet von: address@hidden
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')
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