[sr-dev] [tracker] Task opened: Crash if t_release() is executed after t_relay_to(), when this last returns -1

sip-router admin at sip-router.org
Tue Nov 29 18:57:06 CET 2011


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Iñaki Baz Castillo (ibc) 

Attached to Project - sip-router
Summary - Crash if t_release() is executed after t_relay_to(), when this last returns -1
Task Type - Bug Report
Category - tm
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - All
Severity - High
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Kamailio 3.2 is crashing if t_release() is executed after t_relay_to() returns -1:

---

if ! t_relay_to() {
 t_release();
}

---

Error -1 is generated in t_relay_to, in this case, when trying to reach a domainname which hasn't got a DNS record.


Here the log of the execution of t_relay_to:

ERROR: <core> [resolve.c:1540]: ERROR: sip_hostport2su: could not resolve hostname: "proxy1.jssip.net"
ERROR: tm [ut.h:318]: failed to resolve "proxy1.jssip.net"
ERROR: tm [t_fwd.c:1528]: ERROR: t_forward_nonack: failure to add branches
ERROR: tm [tm.c:1369]: ERROR: w_t_relay_to: t_relay_to failed
WARNING: script | uovyxruroybhnsy | call | t_relay(): -1 generic internal error

This is the log for the execution of t_release():

<core> [mem/q_malloc.c:457]: BUG: qm_free: freeing already freed pointer, first free: tm: h_table.c: free_cell(157) - aborting
ALERT: <core> [main.c:745]: child process 24217 exited by a signal 6
ALERT: <core> [main.c:748]: core was not generated
INFO: <core> [main.c:760]: INFO: terminating due to SIGCHLD
INFO: <core> [main.c:811]: INFO: signal 15 received

More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=184

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.



More information about the sr-dev mailing list