Hello,
On 30/09/15 09:37, huseyin kalyoncu wrote:
Hello Daniel
Thank you for your response. Kamailio from 4.3.2 source tarball I got the core file now. After running backtrace i realized that the problem might be related to our custom module we are developing. Here is the backtrace:
Reading symbols from /usr/local/sbin/kamailio...done. [New LWP 6985] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/local/sbin/kamailio -f /usr/local/etc/kamailio/kamailio.cfg -P /var/run/ka'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __strcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:63 63 ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S: No such file or directory. (gdb) backtrace #0 __strcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:63 #1 0x00007f9aa1f08b09 in vg_digest_authenticate_hdr (msg=0x7f9aaae4eca8, realm=0x7ffe4af97700, hftype=HDR_PROXYAUTH_T, method=0x7f9aaae4ecd0, ahdr=0x7ffe4af976f8) at auth.c:75 #2 0x00007f9aa1f08da8 in w_vg_auth (pmsg=0x7f9aaae4eca8) at auth.c:230
the backtrace shows some functions that don't exist in public kamailio repository (e.g., w_vg_auth()).
I assume you wrote some custom module, the backtrace indicates that the crash is in that code.
Cheers, Daniel