[sr-dev] XMLRPC seg fault

Jason Penton jason.penton at gmail.com
Mon May 19 17:30:53 CEST 2014


Hey Guys,

Please ignore, I suspect this may be related to a problem on my side
(particular mi cmd being called). Will revert.

Cheers
Jason


On Mon, May 19, 2014 at 5:05 PM, Jason Penton <jason.penton at gmail.com>wrote:

> Sorry, I sent the incorrect bt,
>
> (gdb) bt
> #0  0x00007f63b2227e08 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #1  0x00007f63b2229496 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #2  0x00007f63b222d388 in calloc () from /lib/x86_64-linux-gnu/libc.so.6
> #3  0x00007f63b221bcd9 in open_memstream () from
> /lib/x86_64-linux-gnu/libc.so.6
> #4  0x00007f63b2298dcb in __vsyslog_chk () from
> /lib/x86_64-linux-gnu/libc.so.6
> #5  0x00007f63b229941f in syslog () from /lib/x86_64-linux-gnu/libc.so.6
> #6  0x000000000055c7ac in fm_free (qm=0x7f63b12a8010, p=0x7f63b1363738,
> file=0x6486b3 "<core>: parser/parse_via.c", func=0x64aa01 "free_via_list",
> line=2771) at mem/f_malloc.c:576
> #7  0x000000000059c0e8 in free_via_list (vb=0x0) at parser/parse_via.c:2771
> #8  0x00000000005624f7 in clean_hdr_field (hf=0x7f63b13636c0) at
> parser/hf.c:174
> #9  0x0000000000562650 in free_hdr_field_lst (hf=0x7f63b1363858) at
> parser/hf.c:224
> #10 0x000000000056712b in free_sip_msg (msg=0x7fffe0a0d680) at
> parser/msg_parser.c:732
> #11 0x00007f63af7ceb7f in em_receive_request (orig_msg=0x7f63b1396e08,
>     new_buf=0x1ff3e50 "POST sip:127.0.0.1:9 HTTP/1.0\r\nVia: SIP/2.0/TCP
> 10.0.1.163:40594\r\nHost: ZAUbuntu009.it.za.smilecoms.com:6060\r\nContent-Length:
> 183\r\nUser-Agent: Apache XML RPC 3.0 (Lite HTTP
> Transport)\r\nContent-Type: t"..., new_len=394) at xmlrpc.c:2295
> #12 0x00007f63af7cf380 in process_xmlrpc (msg=0x7f63b1396e08) at
> xmlrpc.c:2367
> #13 0x0000000000499a3b in nonsip_msg_run_hooks (msg=0x7f63b1396e08) at
> nonsip_hooks.c:125
> #14 0x00000000004b3ff6 in receive_msg (
>     buf=0x201d430 "POST /RPC2 HTTP/1.0\r\nHost:
> ZAUbuntu009.it.za.smilecoms.com:6060\r\nContent-Length:
> 183\r\nUser-Agent: Apache XML RPC 3.0 (Lite HTTP
> Transport)\r\nContent-Type: text/xml\r\n\r\n<?xml version=\"1.0\"
> encoding=\"UTF-"..., len=349, rcv_info=0x7f636b391a38) at receive.c:161
> #15 0x0000000000542066 in receive_tcp_msg (
>     tcpbuf=0x7f636b391d08 "POST /RPC2 HTTP/1.0\r\nHost:
> ZAUbuntu009.it.za.smilecoms.com:6060\r\nContent-Length:
> 183\r\nUser-Agent: Apache XML RPC 3.0 (Lite HTTP
> Transport)\r\nContent-Type: text/xml\r\n\r\n<?xml version=\"1.0\"
> encoding=\"UTF-"..., len=349, rcv_info=0x7f636b391a38, con=0x7f636b391a20)
> at tcp_read.c:1232
> #16 0x0000000000542fbf in tcp_read_req (con=0x7f636b391a20,
> bytes_read=0x7fffe0a0e1f0, read_flags=0x7fffe0a0e1f4) at tcp_read.c:1387
> #17 0x0000000000544408 in handle_io (fm=0x7f63b1383d38, events=1, idx=-1)
> at tcp_read.c:1559
> #18 0x000000000053d1da in io_wait_loop_epoll (h=0x8f8fe0, t=2, repeat=0)
> at io_wait.h:1092
> #19 0x00000000005452d8 in tcp_receive_loop (unix_sock=34) at
> tcp_read.c:1728
> #20 0x00000000005376d9 in tcp_init_children () at tcp_main.c:4959
> #21 0x0000000000473859 in main_loop () at main.c:1704
> #22 0x0000000000476587 in main (argc=7, argv=0x7fffe0a0e6e8) at main.c:2542
>
>
>
> On Mon, May 19, 2014 at 4:57 PM, Juha Heinanen <jh at tutpro.com> wrote:
>
>> Jason Penton writes:
>>
>> > I see you did a few changes re. XMLRPC recently (end of last month). I
>> am
>> > getting the following (is it related) - if not I will take a look:
>> >
>> > Program terminated with signal 11, Segmentation fault.
>> ...
>> > #6  0x0000000000552dac in destroy_avp_list (list=0x94d420) at
>> usr_avp.c:644
>> > #7  0x0000000000552f3e in reset_avps () at usr_avp.c:678
>> > #8  0x00000000004b4890 in receive_msg (
>> >     buf=0x16f01a0 "POST /RPC2 HTTP/1.0\r\nHost:
>> > ZAUbuntu009.it.za.smilecoms.com:6060\r\nContent-Length:
>> 183\r\nUser-Agent:
>> > Apache XML RPC 3.0 (Lite HTTP Transport)\r\nContent-Type:
>> > text/xml\r\n\r\n<?xml version=\"1.0\" encoding=\"UTF-"..., len=349,
>> > rcv_info=0x7f8a1ba39a38) at receive.c:292
>>
>> did you get any error message to syslog just before the crash?
>>
>> based on the bt, looks like the crash happened before xmlrcp server got
>> the request it.
>>
>> -- juha
>>
>> _______________________________________________
>> sr-dev mailing list
>> sr-dev at lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20140519/6ab944e5/attachment.html>


More information about the sr-dev mailing list