sr-dev June 2014

sr-dev@lists.kamailio.org

21 participants
152 discussions

[tracker] Task closed: CRASH: BUG: qm_free: freeing already freed pointer (0x7fcaeaee3ac0), called from dialog: dlg_cb.c
by sip-router 06 Jun '14

06 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#437 - CRASH: BUG: qm_free: freeing already freed pointer (0x7fcaeaee3ac0), called from dialog: dlg_cb.c User who did this - Daniel-Constantin Mierla (miconda) Reason for closing: Fixed More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=437 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

FS#440 - CRASH: segmentation fault if there is no dispatcher available
by Nuno Reis 06 Jun '14

06 Jun '14

Hi guys. Kamailio apparently segfaults if there is no dispatcher available to take calls. I've just opened another bug report FS#440 for this issue. Happening in kamailio 4.1.3 (642428c) BR, -- *Nuno Miguel Reis* | *Unified Communication** Systems* M. +351 913907481 | nreis(a)wavecom.pt WAVECOM-Soluções Rádio, S.A. Cacia Park | Rua do Progresso, Lote 15 3800-639 AVEIRO | Portugal T. +351 309 700 225 | F. +351 234 919 191 *GPS <http://maps.google.com/maps/ms?msa=0&msid=202333747613191340808.0004b4b227a…> | www.wavecom.pt <http://www.wavecom.pt/>** <http://www.wavecom.pt/>* [image: Description: Description: WavecomSignature] <http://www.wavecom.pt/pt/wavecom/premios.php> [image: Publicity] <http://www.wavecom.pt/pt/mail_eventos.php>

1 0

[tracker] Task opened: CRASH: segmentation fault if there is no dispatcher available (Attachment added)
by sip-router 06 Jun '14

06 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Nuno Miguel Reis (nmreis) Attached to Project - sip-router Summary - CRASH: segmentation fault if there is no dispatcher available Task Type - Bug Report Category - tm Status - Unconfirmed Assigned To - Operating System - Linux Severity - Critical Priority - Normal Reported Version - Development Due in Version - Undecided Due Date - Undecided Details - Kamailio apparently segfaults if there is no dispatcher available to take calls. Please find attached the full backtrace. Happening in kamailio 4.1.3 (642428c) One or more files have been attached. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=440 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[tracker] Comment added: CRASH: dialog module out of bounds issue
by sip-router 06 Jun '14

06 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#438 - CRASH: dialog module out of bounds issue User who did this - Nuno Miguel Reis (nmreis) ---------- I'm using the patch for almost a week and it seems ok now. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=438#comment1504 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[tracker] Comment added: CRASH: BUG: qm_free: freeing already freed pointer (0x7fcaeaee3ac0), called from dialog: dlg_cb.c
by sip-router 06 Jun '14

06 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#437 - CRASH: BUG: qm_free: freeing already freed pointer (0x7fcaeaee3ac0), called from dialog: dlg_cb.c User who did this - Nuno Miguel Reis (nmreis) ---------- I'm using the patch for almost a week and it seems ok now. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=437#comment1503 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

FS#439 - CRASH: segmentation fault after INVITE
by Nuno Reis 06 Jun '14

06 Jun '14

Hi. I've just opened a bug report FS#439 on a segmentation fault after an invite to a uknown DNS domain. It is reproducible and is happening in kamailio 4.1.3 (642428c) Please let me know if anything else is needed. Thanks. -- *Nuno Miguel Reis* | *Unified Communication** Systems* M. +351 913907481 | nreis(a)wavecom.pt WAVECOM-Soluções Rádio, S.A. Cacia Park | Rua do Progresso, Lote 15 3800-639 AVEIRO | Portugal T. +351 309 700 225 | F. +351 234 919 191 *GPS <http://maps.google.com/maps/ms?msa=0&msid=202333747613191340808.0004b4b227a…> | www.wavecom.pt <http://www.wavecom.pt/>** <http://www.wavecom.pt/>* [image: Description: Description: WavecomSignature] <http://www.wavecom.pt/pt/wavecom/premios.php> [image: Publicity] <http://www.wavecom.pt/pt/mail_eventos.php>

1 0

[tracker] Task opened: CRASH: segmentation fault after INVITE (Attachment added)
by sip-router 06 Jun '14

06 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Nuno Miguel Reis (nmreis) Attached to Project - sip-router Summary - CRASH: segmentation fault after INVITE Task Type - Bug Report Category - tm Status - Unconfirmed Assigned To - Operating System - Linux Severity - Critical Priority - Normal Reported Version - 4.1 Due in Version - Undecided Due Date - Undecided Details - Hi. Please find attached a full backtrace on a segmentation fault after an INVITE to an unknown DNS domain. It is reproducible and is happening in kamailio 4.1.3 (642428c) One or more files have been attached. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=439 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

Re: [sr-dev] [SR-Users] Listen on eth alias interface
by Konstantin M. 05 Jun '14

05 Jun '14

I don't think it is a big problem. See my tests: root@milana:~# ip a l 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:50:fc:98:d7:8b brd ff:ff:ff:ff:ff:ff inet 192.168.254.254/24 brd 192.168.254.255 scope global eth1 inet 1.2.3.4/0 brd 255.255.255.255 scope global eth1:0 inet 1.2.3.5/0 brd 255.255.255.255 scope global secondary eth1:2 inet 1.2.3.6/0 brd 255.255.255.255 scope global secondary eth1:test inet 1.2.3.7/0 brd 255.255.255.255 scope global secondary eth1:4:4 3: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether a0:00:00:05:dd:42 brd ff:ff:ff:ff:ff:ff inet 10.10.1.201/20 brd 10.10.15.255 scope global eth2 root@milana:~# gcc -g -Wall -o getifaddrs getifaddrs.c root@milana:~# ./getifaddrs Interface Name : lo Address / Mask : 127.0.0.1 / 255.0.0.0 Interface Name : eth1 Address / Mask : 192.168.254.254 / 255.255.255.0 Interface Name : eth1:0 Address / Mask : 1.2.3.4 / 0.0.0.0 Interface Name : eth1:2 Address / Mask : 1.2.3.5 / 0.0.0.0 Interface Name : eth1:test Address / Mask : 1.2.3.6 / 0.0.0.0 Interface Name : eth1:4:4 Address / Mask : 1.2.3.7 / 0.0.0.0 Interface Name : eth2 Address / Mask : 10.10.1.201 / 255.255.240.0 Test code attached. 2014-06-05 9:31 GMT+04:00 Olle E. Johansson <oej(a)edvina.net>: > > On 04 Jun 2014, at 22:38, Alex Balashov <abalashov(a)evaristesys.com> wrote: > > > On 06/04/2014 04:37 PM, Olle E. Johansson wrote: > >> > >> On 04 Jun 2014, at 22:35, Alex Balashov <abalashov(a)evaristesys.com> > wrote: > >> > >>> Hello Olle, > >>> > >>> Couldn't you get around this by just specifying the IP address of the > interface? e.g. > >>> > >>> listen=udp:xxx.xxx.xxx.xxx:5060 > >> Not in this configuration, but with some tweaking I may. But it would > simplify > >> a lot if I just could point to the interface. > > > > I run into this problem a lot, too, with eth0:x subinterfaces. But > specifying the address is the only way I know of to solve it at present. > > I guess it's about time to file a bug report :-) > > /O > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >

2 1

git:4.1: srdb1: fix memory leak in db-id
by Torrey Searle 04 Jun '14

04 Jun '14

Module: sip-router Branch: 4.1 Commit: 94ebfb5d5973ed59de84ca0e0c87052b4c80f9de URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=94ebfb5… Author: Torrey Searle <tsearle(a)gmail.com> Committer: Torrey Searle <tsearle(a)gmail.com> Date: Mon Jun 2 19:51:19 2014 +0200 srdb1: fix memory leak in db-id - When getting an existing connection from the pool, free the newly created db-id as the pool connection already has a reference to the existing one. Fixes FS#436 (cherry picked from commit 69de17d3bb1d032f9a41752362194d718336e20d) --- lib/srdb1/db.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/lib/srdb1/db.c b/lib/srdb1/db.c index 3eea708..f717464 100644 --- a/lib/srdb1/db.c +++ b/lib/srdb1/db.c @@ -325,6 +325,8 @@ db1_con_t* db_do_init2(const str* url, void* (*new_connection)(), db_pooling_t p pool_insert((struct pool_con*)con); } else { LM_DBG("connection %p found in pool\n", id); + free_db_id(id); // free the new id, as we use the pool instead + id = 0; } res->tail = (unsigned long)con;

1 0

backport of srdb1: fix memory leak in db-id
by Juha Heinanen 04 Jun '14

04 Jun '14

commit of the subject line was not cherry-picked to 4.1. is it so that the leak only exists in master? -- juha

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev June 2014