[omnetpp] Omnet++ crashes on Windows

169 views
Skip to first unread message

Sascha Schulz

unread,
Feb 4, 2008, 10:37:04 AM2/4/08
to omne...@omnetpp.org, Simon Schwarzer, Lukas Pustina
Hi,

I have the following problem with Omnet++ 3.2 and 3.3 on Windows XP
Professional:
When I run my simulation of Queueing Networks Omnet++ crashes in
Express-mode in CmdEnv and TkEnv with a Microsoft problem report in the
ntdll.dll file.
On linux the simulation finishes regularly without any problems. When I run
the simulation with Fastrun for a while and then switch to express it is
also working on windows.
I already examined my simulation with valgrind but no memory leaks were
detected.
Does anyone have an idea what the problem could be? I am pretty clueless at
the moment?

Thanks and kind regards,

Sascha
_______________________________________________
OMNeT++ Mailing List
options: http://lists.omnetpp.org/mailman/listinfo/omnetpp-l
archive: http://www.omnetpp.org/listarchive/index.php

Andras Varga

unread,
Feb 5, 2008, 2:33:55 AM2/5/08
to sch...@cs.uni-bonn.de, OMNeT++ Discussion List
Maybe a stack overflow? Do you use activity()? Just guessing.
Andras

LENIN MEHEDY

unread,
Feb 5, 2008, 5:39:15 AM2/5/08
to OMNeT++ Discussion List
Andras is possibly right because I also faced similar problem before and found the stack overflow problem. I tracked down to the event when it crashes and run the simulation in debug mode. I found that I needed to correct some bugs (e.g. delete unnecessary msgs in my simulation). I hope you have already took care of such mistakes. However, still there might be some problems.

so, try to track down to the event when it crashes. I hope that may give you some clue. The easiest way (brute force) to track down to the event is to run the simulation upto a certain number of events. If it crashes, then run it to a lower value and vice versa. Almost like binary search. However you have try it for several times and face several windows crash :P

when you are near to the event, run the simulation step by step. if you run the simulation in debug mode, you may find the problem during this step-by-step stage.

However, I hope someone may also give you an easier solution.

-Lenin



---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

Maik Wodarz

unread,
Feb 7, 2008, 4:29:25 AM2/7/08
to OMNeT++ Discussion List
You can try also to compile with the debug option and then you start you
simulation with the tool named valgrind. This is a linux tool. But you
can try it under linux with wine. valgrind will you show which object
you crash provoke. Further ist shows you witch methode call is the
reason for your fault. (You can use a CD-Distribution of Linux)
The only thing: I never tried out if a omnetsimulation compiled for
windows runs under wine. I think it is easier to compile without tkenv.

Good look!

Maik

LENIN MEHEDY schrieb:

Andras Varga

unread,
Feb 7, 2008, 4:46:10 AM2/7/08
to OMNeT++ Discussion List
Valginding a Windows executable on Linux over Wine...??? Never tried but
it's probably not going to work, because Valgrind cannot extract the debug
info from an MSVC executable. There may be slightly more chance if the
program was compiled with MinGW...
Reply all
Reply to author
Forward
0 new messages