Anna
unread,Apr 15, 2011, 1:25:25 AM4/15/11Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to omnetpp
Hello!
I've been working on my project in OMNeT++ 4,1, everything is great...
except this error that bogles me:
Simulation terminated with exit code: 139.
I know, I know... It's been written about before. It appears in
different moments of the simulation, not all the time, but very often
lately, and exits the simulation. I have searched online for info on
it and I know it has to do with segmentation faults (memory problems,
right?), but I don't know how to fix it. I installed Valgrind and did
a memcheck with leak-check. There were 60 errors, but all of them came
from the C libraries. I have read in the Valgrind manual that such
errors are likely to appear and, of course, I have no business
changing the C library code.
I thought that maybe I have some mistakes when working with my
classes, not destroying objects when I'm done with them. Is it true
that I have to call the destructor myself, doesn't it jump in by
itself at the right time like in Java? Also, I did call the
destructors to see if this was the problem, but the exit code still
happens.
Can you give me some advice? I'm getting kind of stuck...
Thank you