simulation exit code: 139 e 134

2,024 views
Skip to first unread message

rosaldinho

unread,
Oct 27, 2009, 10:15:22 AM10/27/09
to omnetpp
My simulation exit with those exit code: 139 e 134
What it means?

Patrick Haeflinger

unread,
Oct 27, 2009, 10:33:50 AM10/27/09
to omn...@googlegroups.com
Hi,

With so little information it is difficult to help you ...
Nevertheless using Google you should have been able the find the following :

Exit code 134: The job is killed with an abort signal, and you probably got core dumped. Often this is caused either by an assert() or an ErrMsg(fatal) being hit in your job. There may be a run-time bug in your code. Use a debugger like gdb or dbx to find out what's wrong.
....
Exit code 139: Segmentatation violation.
....

Something is wrong in your code ... use a debugger to see what it's going on !

Patrick


rosaldinho a écrit :

rosaldinho

unread,
Oct 27, 2009, 11:14:35 AM10/27/09
to omnetpp
I run one simulation that i have already runned without error
different time, but now every simulation crashs.
On the consoll appears:
Simulation terminated with exit code: 134
Command line: /home/rosario/omnetpp-4.0/bin/opp_run -r 0 -n /home/
rosario/inetmanet-inetmanet-6d5a094eba5ec0be5f2685f860952bf364042c23/
examples:/home/rosario/inetmanet-
inetmanet-6d5a094eba5ec0be5f2685f860952bf364042c23/src -l /home/
rosario/inetmanet-inetmanet-6d5a094eba5ec0be5f2685f860952bf364042c23/
src/inet /home/rosario/inetmanet-
inetmanet-6d5a094eba5ec0be5f2685f860952bf364042c23/examples/ethernet/
Definitiva2/RTPSMulticast.ini

Working directory: /home/rosario/inetmanet-
inetmanet-6d5a094eba5ec0be5f2685f860952bf364042c23/examples/ethernet/
Definitiva2

LD_LIBRARY_PATH=/home/rosario/omnetpp-4.0/lib::/home/rosario/inetmanet-
inetmanet-6d5a094eba5ec0be5f2685f860952bf364042c23/src:/usr/lib/jvm/
java-6-sun-1.6.0.16/jre/lib/i386/client:/usr/lib/jvm/java-6-
sun-1.6.0.16/jre/lib/i386::/home/rosario/omnetpp-4.0/lib:/home/rosario/
omnetpp-4.0/lib:/usr/lib/xulrunner-addons:/usr/lib/xulrunner-addons
PATH=/home/rosario/omnetpp-4.0/bin::/usr/local/sbin:/usr/local/bin:/
usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/rosario/omnetpp-4.0/bin:/
home/rosario/omnetpp-4.0/bin
OMNETPP_IMAGE_PATH=/home/rosario/omnetpp-4.0/images

On my shell this appears:

*** glibc detected *** /home/rosario/omnetpp-4.0/bin/opp_run:
corrupted double-linked list: 0x09c98900 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb77dc604]
/lib/tls/i686/cmov/libc.so.6[0xb77de367]
/lib/tls/i686/cmov/libc.so.6(cfree+0x96)[0xb77de5b6]
/usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xb79bf231]
/home/rosario/omnetpp-4.0/lib/liboppsimd.so(_ZN7cObjectD0Ev+0x3d)
[0xb7da3779]
/home/rosario/inetmanet-
inetmanet-6d5a094eba5ec0be5f2685f860952bf364042c23/src//libinet.so
(_ZN6Reader13handleMessageEP8cMessage+0x60c)[0xb6e4c83e]
/home/rosario/omnetpp-4.0/lib/liboppsimd.so
(_ZN11cSimulation10doOneEventEP13cSimpleModule+0x1be)[0xb7db9824]
/home/rosario/omnetpp-4.0/lib/libopptkenvd.so
(_ZN5Tkenv22doRunSimulationExpressEv+0x142)[0xb7fcebce]
/home/rosario/omnetpp-4.0/lib/libopptkenvd.so
(_ZN5Tkenv13runSimulationEi7SimTimexP8cMessageP7cModule+0x143)
[0xb7fcf449]
/home/rosario/omnetpp-4.0/lib/libopptkenvd.so
(_Z7run_cmdPvP10Tcl_InterpiPPKc+0x27f)[0xb7fde3ce]
/usr/lib/libtcl8.4.so.0(TclInvokeStringCommand+0x6e)[0xb75ee5ce]
/usr/lib/libtcl8.4.so.0(TclEvalObjvInternal+0x32e)[0xb75ef94e]
/usr/lib/libtcl8.4.so.0[0xb761bd71]
/usr/lib/libtcl8.4.so.0(TclCompEvalObj+0xe8)[0xb7619db8]
/usr/lib/libtcl8.4.so.0(Tcl_EvalObjEx+0xc4)[0xb75f0c24]
/usr/lib/libtcl8.4.so.0(Tcl_IfObjCmd+0x1e0)[0xb75f92c0]
/usr/lib/libtcl8.4.so.0(TclEvalObjvInternal+0x32e)[0xb75ef94e]
/usr/lib/libtcl8.4.so.0[0xb761bd71]
/usr/lib/libtcl8.4.so.0(TclCompEvalObj+0xe8)[0xb7619db8]
/usr/lib/libtcl8.4.so.0(TclObjInterpProc+0x29e)[0xb765207e]
/usr/lib/libtcl8.4.so.0(TclEvalObjvInternal+0x32e)[0xb75ef94e]
/usr/lib/libtcl8.4.so.0[0xb761bd71]
/usr/lib/libtcl8.4.so.0(TclCompEvalObj+0xe8)[0xb7619db8]
/usr/lib/libtcl8.4.so.0(TclObjInterpProc+0x29e)[0xb765207e]
/usr/lib/libtcl8.4.so.0(TclEvalObjvInternal+0x32e)[0xb75ef94e]
/usr/lib/libtcl8.4.so.0[0xb761bd71]
/usr/lib/libtcl8.4.so.0(TclCompEvalObj+0xe8)[0xb7619db8]
/usr/lib/libtcl8.4.so.0(Tcl_EvalObjEx+0xc4)[0xb75f0c24]
/usr/lib/libtk8.4.so.0(TkInvokeButton+0x57)[0xb76d0c67]
/usr/lib/libtk8.4.so.0[0xb76cfb6e]
/usr/lib/libtcl8.4.so.0(TclEvalObjvInternal+0x32e)[0xb75ef94e]
/usr/lib/libtcl8.4.so.0(Tcl_EvalObjv+0x130)[0xb75efc10]
/usr/lib/libtcl8.4.so.0(Tcl_EvalObjEx+0x20b)[0xb75f0d6b]
/usr/lib/libtcl8.4.so.0(Tcl_UplevelObjCmd+0x126)[0xb7651af6]
/usr/lib/libtcl8.4.so.0(TclEvalObjvInternal+0x32e)[0xb75ef94e]
/usr/lib/libtcl8.4.so.0[0xb761bd71]
/usr/lib/libtcl8.4.so.0(TclCompEvalObj+0xe8)[0xb7619db8]
/usr/lib/libtcl8.4.so.0(TclObjInterpProc+0x29e)[0xb765207e]
/usr/lib/libtcl8.4.so.0(TclEvalObjvInternal+0x32e)[0xb75ef94e]
/usr/lib/libtcl8.4.so.0(Tcl_EvalEx+0x4e2)[0xb75f0812]
/usr/lib/libtk8.4.so.0(Tk_BindEvent+0x949)[0xb769f989]
/usr/lib/libtk8.4.so.0(TkBindEventProc+0x15b)[0xb76a635b]
/usr/lib/libtk8.4.so.0(Tk_HandleEvent+0x529)[0xb76aedc9]
/usr/lib/libtk8.4.so.0[0xb76af628]
/usr/lib/libtcl8.4.so.0(Tcl_ServiceEvent+0x8b)[0xb76463eb]
/usr/lib/libtcl8.4.so.0(Tcl_DoOneEvent+0xb9)[0xb7646719]
/home/rosario/omnetpp-4.0/lib/libopptkenvd.so(_Z5runTkP10Tcl_Interp
+0x14)[0xb7fe01b0]
/home/rosario/omnetpp-4.0/lib/libopptkenvd.so(_ZN5Tkenv3runEv+0x8b7)
[0xb7fd0213]
/home/rosario/omnetpp-4.0/lib/liboppenvird.so
(_ZN9EnvirBase3runEiPPcP14cConfiguration+0x194)[0xb7f45922]
/home/rosario/omnetpp-4.0/lib/liboppenvird.so
(_Z18setupUserInterfaceiPPcP14cConfiguration+0xdea)[0xb7f3cf4b]
/home/rosario/omnetpp-4.0/lib/liboppenvird.so(main+0x64)[0xb7f3de10]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7783775]
/home/rosario/omnetpp-4.0/bin/opp_run[0x80486b1]
======= Memory map: ========
08048000-08049000 r-xp 00000000 08:03 141672 /home/rosario/
omnetpp-4.0/bin/opp_run
08049000-0804a000 r--p 00000000 08:03 141672 /home/rosario/
omnetpp-4.0/bin/opp_run
0804a000-0804b000 rw-p 00001000 08:03 141672 /home/rosario/
omnetpp-4.0/bin/opp_run
0841d000-09ca6000 rw-p 0841d000 00:00 0 [heap]
b5200000-b5221000 rw-p b5200000 00:00 0
b5221000-b5300000 ---p b5221000 00:00 0
b535a000-b5eb1000 rw-p b535a000 00:00 0
b5eb1000-b5f91000 r-xp 00000000 08:03 1232848 /usr/lib/libBLT.
2.4.so.8.4
b5f91000-b5f92000 r--p 000df000 08:03 1232848 /usr/lib/libBLT.
2.4.so.8.4
b5f92000-b5fa3000 rw-p


On 27 Ott, 15:33, Patrick Haeflinger <patrick.haeflin...@alcatel-
lucent.fr> wrote:
> Hi,
>
> With so little information it is difficult to help you ...
> Nevertheless using Google you should have been able the find the following :
>
> *Exit code 134:* The job is killed with an abort signal, and you
> probably got core dumped. Often this is caused either by an |assert()|
> or an |ErrMsg(fatal)| being hit in your job. There may be a run-time bug
> in your code. Use a debugger
> <http://www.slac.stanford.edu/BFROOT/www/doc/workbook/debug/debug.html>
> like gdb or dbx to find out what's wrong.
> ....
> *Exit code 139:* Segmentatation violation.

Andreas Köpke

unread,
Oct 27, 2009, 11:23:27 AM10/27/09
to omn...@googlegroups.com, rosaldinho
Run it through valgrind. You caused some error in memory that leads to a crash
much later.

Patrick Haeflinger

unread,
Oct 27, 2009, 11:23:36 AM10/27/09
to omn...@googlegroups.com
At least something may have changed as it is not working anymore...
The best thing to do is to launch this simulation with the debugger in order to see where the crash occurs (see the stack trace)

Patrick

rosaldinho a écrit :
Reply all
Reply to author
Forward
0 new messages