Exit code 134!!!!

1,978 views
Skip to first unread message

Alessandro Corsi

unread,
Jan 30, 2015, 5:44:54 AM1/30/15
to omn...@googlegroups.com
Hi guys,
I have a problem with my simulation. When I strart it, it processes a lot of packets without problems, but suddendly it crashes with the following error:

unable to alloc 5376 bytes
Simulation terminated with exit code: 134

I have tried to use the debugger and I have the following answers:

Thread [2] 2918 [core: 1] (Suspended: Container)
No source available for "_kernel_vsyscall() at 0xb7fdd424"
No source available for "select() at 0xb78f4bd1"
No source available for "0xb7635279"
No source available for "start_thread() at 0xb77f7d4c"
No source available for "clone() at 0xb78fbbae"

Thread[1] 2914 [core: 1] (Suspended: Signal: SIGABRT: Aborted)

I tried my simulation step by step to see if it works fine and it works like I want.
My nework is very simple, so I don't understand the reason of this problem.
Please help me!



Michael Kirsche

unread,
Jan 30, 2015, 7:45:36 AM1/30/15
to omn...@googlegroups.com
Maybe you wrote past some variable / array.

The "answer" from the debugger for the other thread (that aborted with SIGABRT) is more important by the way.

I would recommend to check the code where the actual abort signal occurred.

I would also recommend to use Valgrind (under Linux), it will probably show you your error right away (using the leak checker).
Reply all
Reply to author
Forward
0 new messages