[SR-Users] Core/ signal 11 Segmenation fault on kamailio 4.3.5

Daniel-Constantin Mierla miconda at gmail.com
Wed Aug 17 17:18:58 CEST 2016


Hello,

there should be a kamailio-dbg or kamailio-debug rpm/deb package than
can be installed to get the debugging symbols. Install that and grab
again the backtrace to get some useful details.

Cheers,
Daniel


On 17/08/16 16:40, Dragos Oancea wrote:
> Hi,
>
> The backtrace is not very useful, there are no debugging symbols.
> You probably installed a kamailio RPM on that machine. Try to compile
> directly on the machine and reproduce.
>
> Cheers,
> Dragos
>
> On 17/08/2016 14:16, Jonathan Hunter wrote:
>> Hi guys,
>>
>> We seem to have a regular occurrence where one of the child processes is
>> crashing, and causing a coredump.
>>
>> Please see the output of the corefile;
>>
>>  gdb kamailio /core.31568
>> GNU gdb (GDB) Red Hat Enterprise Linux (7.2-83.el6)
>> Copyright (C) 2010 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later
>> <http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
>> and "show warranty" for details.
>> This GDB was configured as "x86_64-redhat-linux-gnu".
>> For bug reporting instructions, please see:
>> <http://www.gnu.org/software/gdb/bugs/>...
>> Reading symbols from /usr/sbin/kamailio...(no debugging symbols
>> found)...done.
>> [New Thread 31568]
>> Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from
>> /usr/lib                                                                
>>                /debug/lib64/ld-2.12.so.debug...done.
>> done.
>> Loaded symbols for /lib64/ld-linux-x86-64.so.2
>> Core was generated by `/usr/sbin/kamailio -P
>> /var/run/kamailio/kamailio.pid -f /                                    
>>                                            /etc/kamailio//kamaili'.
>> Program terminated with signal 11, Segmentation fault.
>> #0  0x00000000004deefd in send_fd ()
>> (gdb) bt full
>> #0  0x00000000004deefd in send_fd ()
>> No symbol table info available.
>> #1  0x00000000004e0bc1 in pp_substdef_add ()
>> No symbol table info available.
>> #2  0x00000000004da13c in build_res_buf_from_sip_req ()
>> No symbol table info available.
>> #3  0x00007fc99099f4a1 in ?? ()
>> No symbol table info available.
>> #4  0x00000000921cd3c8 in ?? ()
>> No symbol table info available.
>> #5  0x00007fc9921cd3f8 in ?? ()
>> No symbol table info available.
>> #6  0x0000000000415eb0 in do_action ()
>> No symbol table info available.
>> #7  0x00007fc9909a2841 in ?? ()
>> No symbol table info available.
>> #8  0x00007fc991faf030 in ?? ()
>> No symbol table info available.
>> #9  0x0000000000000004 in ?? ()
>> No symbol table info available.
>> #10 0x0000000000000001 in ?? ()
>> No symbol table info available.
>> #11 0x0000000000000002 in ?? ()
>>
>>
>> The last transaction appears to be a REGISTER message from a User-Agent:
>> SIPAUA/0.1.001 which runs on an android device.
>>
>> We are looking to reproduce in lab environment but I just wondered if
>> anyone had seen this on this version?  Or can advise on the core dump
>> output?
>>
>> Thanks
>>
>> Jon
>>
>>
>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users at lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
http://www.asipto.com - http://www.kamailio.org
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda




More information about the sr-users mailing list