Yes indeed seems to fix the problem. Thanks.
Jan
Anthony Messina schreef op 2014-11-29 19:08:
You fix does seem to resolve the issue. Thank you. -A
On Wednesday, November 26, 2014 04:42:29 PM Daniel-Constantin Mierla
wrote:
Hello,
can you give it a try to the patch from next commit?
http
You fix does seem to resolve the issue. Thank you. -A
On Wednesday, November 26, 2014 04:42:29 PM Daniel-Constantin Mierla wrote:
> Hello,
>
> can you give it a try to the patch from next commit?
>
> http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=9a46223c
> 077c8d058cdc633
Hello,
can you give it a try to the patch from next commit?
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=9a46223c077c8d058cdc633563b0d9f14af332ae
Let me know if all works fine in order to backport.
Cheers,
Daniel
On 26/11/14 00:54, Anthony Messina wrote:
> On Tuesday, No
On Tuesday, November 25, 2014 11:43:36 PM Daniel-Constantin Mierla wrote:
> Hello,
>
> finally got to it -- the double free message is printed when destroying the
> sip message. Quickly looking at the code, the r-uri, ruid, user-agen and
> dst-uri (and some other attributes of the first branch, bu
Hello,
finally got to it -- the double free message is printed when destroying
the sip message. Quickly looking at the code, the r-uri, ruid, user-agen
and dst-uri (and some other attributes of the first branch, but perhaps
not available in that case) are very likely to be freed twice -- I will
tr
No problem, Daniel. Thanks again for hekping us out. -A
Quoting Daniel-Constantin Mierla :
Unfortunately I didn't have time to analyze -- it may still take a bit,
being traveling with a broken laptop.
Cheers,
Daniel
On 17/11/14 22:49, Anthony Messina wrote:
On Tuesday, November 11, 2014 09
Unfortunately I didn't have time to analyze -- it may still take a bit,
being traveling with a broken laptop.
Cheers,
Daniel
On 17/11/14 22:49, Anthony Messina wrote:
> On Tuesday, November 11, 2014 09:29:26 AM Daniel-Constantin Mierla wrote:
>> looks like there is a double free, which, although
On Tuesday, November 11, 2014 09:29:26 AM Daniel-Constantin Mierla wrote:
> looks like there is a double free, which, although is good to find and
> fix, is normally safe for runtime.
>
> Can you set debug=3 and send all the log messages here?
>
> Cheers,
> Daniel
Daniel, were the logs that we p
Hello,
looks like there is a double free, which, although is good to find and
fix, is normally safe for runtime.
Can you set debug=3 and send all the log messages here?
Cheers,
Daniel
On 10/11/14 18:56, J Hazenberg wrote:
> Hello,
>
> I'm runnig kamailio 4.2.0 and using the lookup_branches func
On Monday, November 10, 2014 11:35:11 PM Anthony Messina wrote:
> On Monday, November 10, 2014 06:56:08 PM J Hazenberg wrote:
> > Hello,
> >
> >
> >
> > I'm runnig kamailio 4.2.0 and using the lookup_branches function from
> > the register module to lookup all branches after a alias_db_lookup. Th
On Monday, November 10, 2014 06:56:08 PM J Hazenberg wrote:
> Hello,
>
> I'm runnig kamailio 4.2.0 and using the lookup_branches function from
> the register module to lookup all branches after a alias_db_lookup. The
> function seems to work fine but i see the following error in the log
> file
Hello,
I'm runnig kamailio 4.2.0 and using the lookup_branches function from
the register module to lookup all branches after a alias_db_lookup. The
function seems to work fine but i see the following error in the log
file just after the lookup:
INFO: [mem/f_malloc.c:599]: fm_free(): freein
12 matches
Mail list logo
