Simulation stops after 42 s

[rport...@gmail.com]

Hi,

I've successfully ran the road and network simulations and everything is working as they should and with the expected results, however after 42s the simulation crashes and gives a 139 error. I have searched for this before and I know that it is related to a segmentation fault or a pointer which was pointing to a memory location which is now deleted. But I can't understand how I'm going to solve the problem.

If everything is working well, how will I know at which section in my code is returning this error after being run and used repeadly before it returns this error?

Any suggestions please?

Thanks in advance

[Rudolf Hornig]

Perhaps running it in debugger would show some hints?

[Rebecca Portelli]

Hi  Mr.Hornig,

I have found the problem. At time 41 car[0] is exiting the simulation and its self messages that had already been scheduled are still in the schedule event in the simulation, they are not deleted. And when it comes to them, the program crashes and then I get the error 139.

In those self messages I can see: ... selmsg for <deleted module> ...

How can I fix this problem please? And how do I remove the pointers that are point to a car after that car exits the simulation, so that those messages are deleted from the schedule event, please?

Thanks in advance

--
--
Sent from the OMNeT++ mailing list. To configure your membership,
visit http://groups.google.com/group/omnetpp
 
---
You received this message because you are subscribed to a topic in the Google Groups "omnetpp" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/omnetpp/9BxkRFJ37WU/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to omnetpp+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Rebecca Portelli]

Nevermind I have fixed the problem. It was because of the car leaving the simulation, but it wasn't because of the self messages. It was because of a topology list that I created, and I wasn't updating it correctly.

Thanks anyway!