[OpenSIPS-Devel] Need help interpreting a GDB backtrace

[Răzvan Crainea]

Hi, Peter!

Can you post the syslog lines before the OpenSIPS crash?
Also, can you contact me on #opensips on Freenode, so we can speed the 
things up? My nick is razvanc.

Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 03/31/2015 11:30 PM, Peter Kust wrote:
>
> Greetings.
>
> I’m working on identifying an odd system crash that has been happening 
> on my proxy server today (v1.11.1 running on CentOS 6.6).  I have 
> experienced a series of events where OpenSIPS terminates on a signal 
> 6.  I’ve been able to get a core dump on the last event, and a 
> backtrace of that core looks as follows:
>
> (gdb) bt
>
> #0  0x00007ffca8f17625 in raise () from /lib64/libc.so.6
>
> #1  0x00007ffca8f18e05 in abort () from /lib64/libc.so.6
>
> #2  0x00000000004d525b in qm_debug_frag (qm=0x7ffca8ce4010, f=<value 
> optimized out>) at mem/q_malloc.c:164
>
> #3  0x00000000004d5ebf in qm_free (qm=0x7ffca8ce4010, 
> p=0x7ffca8e17af8, file=0x7ffca21b319c "sca_logic.c", 
> func=0x7ffca21b32d0 "sca_logic_notify", line=632) at mem/q_malloc.c:457
>
> #4  0x00007ffca21a95ca in sca_logic_notify (params=<value optimized 
> out>, b2b_event=16) at sca_logic.c:632
>
> #5  0x00007ffca23df919 in b2b_logic_notify_reply (src=<value optimized 
> out>, msg=<value optimized out>, key=<value optimized out>, 
> body=0x7fffe27f09e0, extra_headers=0x7fffe27f09d0, b2bl_key=<value 
> optimized out>, hash_index=272,
>
>     local_index=0) at logic.c:1262
>
> #6  0x00007ffca23e04a0 in b2b_logic_notify (src=1, msg=0x7ffca8e04240, 
> key=0x7ffc9fdef400, type=<value optimized out>, param=0x7fffe27f13c0) 
> at logic.c:2043
>
> #7  0x00007ffca2610224 in b2b_tm_cback (t=0x7ffca0252278, 
> htable=0x7ffc9fe36688, ps=<value optimized out>) at dlg.c:2685
>
> #8  0x00007ffca5e0c475 in run_trans_callbacks (type=256, 
> trans=0x7ffca0252278, req=<value optimized out>, rpl=<value optimized 
> out>, code=<value optimized out>) at t_hooks.c:212
>
> #9  0x00007ffca5e2dccc in local_reply (t=0x7ffca0252278, p_msg=<value 
> optimized out>, branch=<value optimized out>, msg_status=<value 
> optimized out>, cancel_bitmap=<value optimized out>) at t_reply.c:1464
>
> #10 0x00007ffca5e2f06d in reply_received (p_msg=0x7ffca8e04240) at 
> t_reply.c:1614
>
> #11 0x000000000042da8c in forward_reply (msg=0x7ffca8e04240) at 
> forward.c:575
>
> #12 0x0000000000478bf7 in receive_msg (buf=<value optimized out>, 
> len=<value optimized out>, rcv_info=<value optimized out>) at 
> receive.c:214
>
> #13 0x00000000004cd9e2 in udp_rcv_loop () at udp_server.c:422
>
> #14 0x0000000000434f63 in main_loop (argc=<value optimized out>, 
> argv=<value optimized out>) at main.c:942
>
> #15 main (argc=<value optimized out>, argv=<value optimized out>) at 
> main.c:1634
>
> There aren’t any out of memory warnings in the log file.  The signal 6 
> abort is raised and then OpenSIPS just crashes.
>
> Cordially,
>
> Peter Nayland Kust
>
> Director of Technologies
>
> BusinesSuites
>
> 24624 Interstate 45 North, Suite 200
>
> Houston, TX 77386
>
> *Tel:*281.378.8051
>
> *Fax:*855.287.6961
>
> *peter.kust at businessuites.com *
>
>
>
> _______________________________________________
> Devel mailing list
> Devel at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20150401/8c005c39/attachment.htm>