[SR-Users] Possible memory leak in siptrace module in kamailio 5.1/5.2

Daniel-Constantin Mierla miconda at gmail.com
Wed May 15 13:02:47 CEST 2019


Hello,

On 15.05.19 09:43, Thomas Weber wrote:
> Great that you can use this workaround. 
> Although i'm a bit confused because KSR.siptrace.sip_trace() is not supposed to accept a string parameter.

If the parameter is given, then it is ignored -- with scripting
languages allowing dynamic number of parameters is not easy to detect at
init/startup if a function has too many params.

Anyhow, in this case I discovered that a local variable was not freed -
I pushed a patch to branch 5.2, master branch was changed a lot and
doesn't have the same kind of code. Can anyone test and report if works
ok or not?

Cheers,
Daniel

>
> Can you file a bug on github regarding sip_trace_dst()?
>
> ----- Ursprüngliche Mail -----
>> Actually so far it seems using KSR.siptrace.sip_trace("sip:<myhomerip>:9060")
>> instead of KSR.siptrace.sip_trace_dst("sip:<myhomerip>:9060"), fixes it ! I'm
>> rolling it out on more systems to be sure, and wait a bit longer to be very
>> sure. But thx for the help!
>>
>>
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda




More information about the sr-users mailing list