[Serdev] core dump with lcr module

[Christopher Crawford]

-----Original Message-----
From:	Juha Heinanen [mailto:jh at tutpro.com]
Subject:	[Serdev] core dump with lcr module
Christopher Crawford writes:

>> I am seeing a core dump when using the lcr module, next_gw routine
>> only in a failure_route.  

>are you saying that you don't call next_gw() first time in route block
>before entering a failure route block?

See next_gw() calling routes below taken from ser.cfg .

>> It seems to be related to adding a new via
>> header.  In the configuration, I have simplified it to have one group
>> and two gateways.  The dump occurs on a t_on_failure callback, when
>> next_gw is called to route to the second gateway.  Below is the back
>> trace.

>back trace doesn't show next_gw() call.

Right.  Yes, the dump occurs after the next_gw() call, after a do_action call.

> try if it works in rel_0_9_0 with lcr backport
> http://tutpro.com/tmp/lcr-0.9.0.tgz

I will, after this email.


<<<<<<<<<<<< originating route

route[5]
{
     record_route();
     setflag(5);
 
    if( from_gw() )  # This is used to escape from gateway loops.
    {
        sl_send_reply("480", "Route from gateway to unknown subscriber. ");
    }
    else
    {
          if (!load_gws( ) ) {
              sl_send_reply("500", "Server Internal Error - Cannot load gateways");
              break;
           };
           if ( !next_gw( ) ) {
              sl_send_reply("502","No Gateway configured");
              break;
           }
           t_on_failure("6" );
    }
    break;
}



<<<<<<<<<<<< call back below

failure_route[6]
{
        if( t_check_status( "408" ) || t_check_status( "480" ) || t_check_status( "502" ) || t_check_status( "404" ) )
        {
        if( !next_gw( ) )
        {
              t_reply("503", "Service not available - No more gateways");
              break;
        }
        t_on_failure("6" );
        }
        t_relay( );
}