Skip to main content

RI crash on gdb enabled Linux build

Please note these forums are being decommissioned and use the new and improved forums at
1 reply [Last post]
Joined: 2011-07-31


While running the latest RI in linux with gdb enabled,RI is getting crashed during boot up itself. If GDB is not enabled, it is working fine. I have done the testing with GNU gdb (GDB) Fedora (7.0-3.fc12) and GNU gdb (GDB) Fedora (7.0.1-50.fc12)

The gdb back trace obtained during crash is as follows.

Program received signal SIGUSR2, User defined signal 2.
[Switching to Thread 0x904f9b70 (LWP 13940)]
0x003b2424 in __kernel_vsyscall ()
#0 0x003b2424 in __kernel_vsyscall ()
#1 0x0084df08 in accept () from /lib/
#2 0x03ef7efd in mpeos_socketAccept (socket=54, address=0x904f90e8,
address_len=0x904f90f8) at ../RI_Linux/mpeos_socket.c:354
#3 0x027f4feb in Java_java_net_PlainSocketImpl_socketAccept ()
from /w/tdkdev--custom--test--RI_custom_lnx/ri.inst2/ocap-ri/ocap/bin/CableLabs/simulator/Linux/debug/env/cvm/bin/
#4 0x027fe6eb in args_done ()
from /w/tdkdev--custom--test--RI_custom_lnx/ri.inst2/ocap-ri/ocap/bin/CableLabs/simulator/Linux/debug/env/cvm/bin/
#5 0xb7472984 in ?? ()
#6 0x9422deb4 in ?? ()
#7 0x9422deb8 in ?? ()
#8 0x9422debc in ?? ()
#9 0x9cbf2120 in ?? ()
#10 0xb7472958 in ?? ()
#11 0x904f91b8 in ?? ()
#12 0x0276fa9a in CVMinvokeJNIHelper ()

Is anyone facing the same issue? The complete log is attached here with (ri_console_log_gdbCrash.txt).

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2008-03-05

This has been fixed with r29956:

r29956 | mkorzen | 2012-02-21 10:58:56 -0800 (Tue, 21 Feb 2012) | 1 line
Changed paths:
M /OCAPRI/trunk/ri/RI_Platform/platform.cfg
M /OCAPRI/trunk/ri/RI_Platform/

OCORI-4110, RISK-na: Do not process SIGUSR1 and SIGUSR2 process signals when running in GDB.

You can get the latest version of the script from trunk and overwrite your local copy with it - that should fix the issue...

Best -