[SR-Users] segfault in siptrace module using setflag?

samuel samu60 at gmail.com
Tue Oct 9 15:26:33 CEST 2012


These are the lines printed, as you can see there isn't yet a rtpproxy
running but it has been working in the tests without crashing. The config
is pretty standard so you'll see the usual routes. I've printed the line
number for an easy debugging.
I'm not 100% sure that it always happens in the same point. I'll try to
reproduce it and see whether following errors happen in the same point of
the config file.

Oct  9 15:16:25 kamailio1 kamailio[18015]: WARNING: rtpproxy
[rtpproxy.c:1393]: can't get version of the RTP proxy
Oct  9 15:16:25 kamailio1 kamailio[18015]: WARNING: rtpproxy
[rtpproxy.c:1430]: support for RTP proxy <udp:127.0.0.1:7722> has been
disabled temporarily
Oct  9 15:16:25 kamailio1 kamailio[18015]: ERROR: rtpproxy
[rtpproxy.c:2231]: no available proxies
Oct  9 15:16:25 kamailio1 kamailio[18015]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=832 a=17 n=if
Oct  9 15:16:25 kamailio1 kamailio[18015]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=827 a=25 n=is_request
Oct  9 15:16:25 kamailio1 kamailio[18015]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=831 a=17 n=if
Oct  9 15:16:25 kamailio1 kamailio[18015]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=828 a=25 n=has_totag
Oct  9 15:16:25 kamailio1 kamailio[18015]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=829 a=26 n=add_rr_param
Oct  9 15:16:25 kamailio1 kamailio[18015]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=838 a=17 n=if
Oct  9 15:16:25 kamailio1 kamailio[18015]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=832 a=25 n=is_reply
Oct  9 15:16:25 kamailio1 kamailio[18015]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=838 a=3 n=return
Oct  9 15:16:25 kamailio1 kamailio[18015]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=971 a=3 n=exit
Oct  9 15:16:25 kamailio1 kernel: [6556004.157495] kamailio[18015] general
protection ip:532b74 sp:7fffbd33ded0 error:0 in kamailio[400000+207000]
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=988 a=26 n=xdbg
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=991 a=17 n=if
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=990 a=6 n=route
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=822 a=17 n=if
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=815 a=25 n=is_request
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=825 a=17 n=if
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=822 a=42 n=isflagset
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=825 a=25 n=rtpproxy_manage
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=832 a=17 n=if
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=827 a=25 n=is_request
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=838 a=17 n=if
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=832 a=25 n=is_reply
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=836 a=17 n=if
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=833 a=26 n=isbflagset
Oct  9 15:16:25 kamailio1 kamailio[18006]: ERROR: *** cfgtrace:
c=[/usr/local/etc/kamailio/kamailio.cfg] l=838 a=3 n=return
Oct  9 15:16:26 kamailio1 kamailio[18019]: : <core> [pass_fd.c:293]: ERROR:
receive_fd: EOF on 29
Oct  9 15:16:26 kamailio1 kamailio[18001]: ALERT: <core> [main.c:785]:
child process 18015 exited by a signal 11
Oct  9 15:16:26 kamailio1 kamailio[18001]: ALERT: <core> [main.c:788]: core
was generated


route[NATMANAGE] {
#!ifdef WITH_NAT
        if (is_request()) {
                if(has_totag()) {
                        if(check_route_param("nat=yes")) {
                                setbflag(FLB_NATB);
                        }
                }
        }
        if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB)))
                return;

        rtpproxy_manage();

827:        if (is_request()) {
                if (!has_totag()) {
                        add_rr_param(";nat=yes");
                }
831:        }
        if (is_reply()) {
                if(isbflagset(FLB_NATB)) {
                        fix_nated_contact();
                }
        }
#!endif
838:        return;
}

959:route[RELAY_TO_PSTN] {

        # enable additional event routes for forwarded requests
        # - serial forking, RTP relaying handling, a.s.o.
        if (is_method("INVITE|SUBSCRIBE")) {
                t_on_branch("MANAGE_BRANCH");
                t_on_reply("MANAGE_REPLY");
        }

        if (!t_relay()) {
                sl_reply_error();
        }
971:        exit;
}


route[HOMER] {
        setflag(22);
        sip_trace();
}

# manage outgoing branches
branch_route[MANAGE_BRANCH] {
        xdbg("new branch [$T_branch_idx] to $ru\n");
        route(NATMANAGE);
}

# manage incoming replies
onreply_route[MANAGE_REPLY] {
988:        xdbg("incoming reply\n");
        if(status=~"[12][0-9][0-9]")
                route(NATMANAGE);
991:}


On 9 October 2012 15:11, samuel <samu60 at gmail.com> wrote:

> The output of the requested command is:
> (gdb) p *a
> Cannot access memory at address 0x485f3832315f4d43
>
> I'll try to load  the debugger module, and send the requested information
> to digg into the problem.
>
> Thanks again!
> SAmuel.
>
>
> On 9 October 2012 13:25, Daniel-Constantin Mierla <miconda at gmail.com>wrote:
>
>> The line matches the access to the action, can you send also the output
>> inside gdb for command:
>>
>> p *a
>>
>> Also, as I understand you can reproduce it, can you load debugger module,
>> set its parameter cfg_trace to 1 and run again. Then send the lines printed
>> by the cfg trace before the crash, so I can track what actions in the
>> config were executed.
>>
>> Daniel
>>
>>
>> On 10/9/12 1:01 PM, samuel wrote:
>>
>>> This is the output of the core file:
>>>
>>> (gdb) bt full
>>> #0  do_action (h=<value optimized out>, a=0x485f3832315f4d43, msg=<value
>>> optimized out>) at action.c:340
>>>
>>
>> --
>> Daniel-Constantin Mierla - http://www.asipto.com
>> http://twitter.com/#!/miconda - http://www.linkedin.com/in/**miconda<http://www.linkedin.com/in/miconda>
>> Kamailio Advanced Training, Berlin, Nov 5-8, 2012 -
>> http://asipto.com/u/kat
>> Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 -
>> http://asipto.com/u/katu
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20121009/457b2ba9/attachment-0001.htm>


More information about the sr-users mailing list