Module: sip-router
Branch: 3.2
Commit: 609b0aa86624416828c0c117e0cfdbeb7643bcb8
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=609b0aa…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Thu Nov 17 23:14:32 2011 +0100
tm: free path if set first time in a branch route
(cherry picked from commit 7b612d999e061d05b60054e7749052d0abdf514c)
---
modules/tm/t_fwd.c | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/modules/tm/t_fwd.c b/modules/tm/t_fwd.c
index 210601d..26bf7f3 100644
--- a/modules/tm/t_fwd.c
+++ b/modules/tm/t_fwd.c
@@ -374,6 +374,10 @@ static int prepare_new_uac( struct cell *t, struct sip_msg *i_req,
ignored) */
next_hop=&i_req->dst_uri;
}
+ /* no path vector initially, but now is set after branch route and
+ * callbacks execution */
+ if(i_req->path_vec.s!=0 && free_path==0)
+ free_path=1;
}else{
/* no branch route and no TMCB_REQUEST_FWDED callback => set
msg uri and path to the new values (if needed) */
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#179 - segfault in tm/timers?
User who did this - Bayan Towfiq (btowfiq)
----------
Seems to be corrupted -- Can these errors shed any light? ERROR: slow timer too slow: overflow (44155 - 43132 = 1023)
This was something very random and i'm not sure if i'll be able to reproduce it.
(gdb) p*cbp
Cannot access memory at address 0x732d336c6576656c
(gdb) x/16xg cbp
0x732d336c6576656c: Cannot access memory at address 0x732d336c6576656c
(gdb) x/16ag cbp
0x732d336c6576656c: Cannot access memory at address 0x732d336c6576656c
(gdb) x cb_lst->first
Cannot access memory at address 0x0
(gdb)
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=179#comment380
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#179 - segfault in tm/timers?
User who did this - Ovidiu Sas (osas)
----------
Take a look at this gdb tutorial:
http://www.delorie.com/gnu/docs/gdb/gdb_56.html
Try to print the content of the memory before and after the cbp and see if there is something that you recognize there:
x/16xg cbp
x/16ag cbp
also, check the value of cb_lst->first to see if it's valid.
Most likely the memory was corrupted by another call and this particular call just crashed the server.
If this is the case, the core dump is not very useful because the crash doesn't capture the cause, only the effect :(
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=179#comment379
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#173 - Double Free -- Crash/Coredump and possible security vulnerability
User who did this - Daniel-Constantin Mierla (miconda)
----------
Also, I just pushed in a tmp branch (tmp/dlgnewref) a patch refactoring the dlg structure reference counting, mainly in relation with TM module. The commit link is:
* http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=9ba…
This approach should be safer for any future development of tm, as there is no more storage of a dialog module specific pointer inside TM structures. Also, dialog structures destroyed for various reasons, will be no longer found by tm callbacks or timer functions, thus no more risk of segmentation fault.
Testing of this new version will appreciated. Based on results and feedback, it will be merged into master branch and backported -- there is no change in config functionality or exported API of dialog module -- just internal refactoring.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=173#comment378
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.