THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#184 - Crash if t_release() is executed after t_relay_to(), when this last returns -1
User who did this - Daniel-Constantin Mierla (miconda)
----------
I looked yesterday evening and couldn't spot it by eye. Now I could test it and does not crash. Can you get the full log with debug=3? Maybe you can get the core file as well -- run as root, with ulimit -c unlimited.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=184#comment429
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.
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.
Hello,
development guide for Kamailio has been updated for v3.2.0 - it goes
through internal components, presenting the APIs for pkg/shm memory,
locking/synchronization, config file interpreter, database connectors,
a.s.o., as well as guiding how to write a new module. There is a section
trying to collect hints about upgrading a module developed for old
versions 1.x to newer architecture and APIs in versions 3.x.
The tutorial is available online at:
* http://asipto.com/u/kdg
A mirror is hosted at:
* http://www.kamailio.org/docs/kamailio-devel-guide/
This is the first release for v3.2, it may get adjustments in the near
future. Among the plans to add new chapters: how to write docbook
documentation; TM module API, Presence module API ...
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#173 - Double Free -- Crash/Coredump and possible security vulnerability
User who did this - Bayan Towfiq (btowfiq)
----------
will the dlgnewref also be merged?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=173#comment428
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#105 - $Ts returns wrong timestamp
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=105
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#105 - $Ts returns wrong timestamp
User who did this - Daniel-Constantin Mierla (miconda)
----------
PID was added to be sure the caching of the time will not overlap for different messages (now in master, 3.2 and 3.1).
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=105#comment427
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#119 - named flags not working for at least acc module
User who did this - Daniel-Constantin Mierla (miconda)
----------
I change this report to improvement -- names for flags were specific to SER flavour, while in Kamailio is now possible to use #!define to alias a string ID to a flag index. Not sure named flags makes sense to keep anymore.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=119#comment426
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.