THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#299 - modules/debugger: be able to log assign actions
User who did this - Daniel-Constantin Mierla (miconda)
----------
The first three patches look ok, they can be committed.
For the 4th patch I think the cache has to be in private memory, kept by each process (practically, using pkg and no need anymore for locks). I was thinking a bit more about it, and some modules can add items in PV cache (in the core) at runtime (like app_lua). Although the ones used in config should be core PV cache from startup, still there is a potential that a module uses actions inside at runtime and can end up in some assignment.
By the nature of pv_spec that can have pkg alloc'ed content, keeping in share memory a reference to it might lead to a different process accessing it than the one that added it in core PV cache.
If kept in pkg, the debugger pv assign cache can hold only the pv_spec pointer and the name can be taken computing the offset in core pv cache structure relative to it (or simply keep a pointer to the whole structure or directly to the name).
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=299#comment910
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#300 - Kamailio crash when module topoh module is loaded and removing Via headers in reply route with remov
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
Additional comments about closing: Reopen if still an issue.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=300
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#300 - Kamailio crash when module topoh module is loaded and removing Via headers in reply route with remov
User who did this - Daniel-Constantin Mierla (miconda)
----------
I added a safety check for it in master and 4.0 branches. You have to use git branches to test if works ok for you.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=300#comment909
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#299 - modules/debugger: be able to log assign actions
User who did this - Víctor Seva (linuxmaniac)
----------
Patches refreshed.
Now I don't call pv_parse_spec/pv_parse_spec2 on patch 0001.
Added a while loop inside the FOR on patch 0003.
Thanks Daniel for your reviews
----------
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=299#comment908
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 - Guillaume Bour (gbour)
Attached to Project - sip-router
Summary - Kamailio crash when module topoh module is loaded and removing Via headers in reply route with remov
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - Low
Priority - Normal
Reported Version - 4.0
Due in Version - Undecided
Due Date - Undecided
Details - Reproduceable on kamailio 4.0.0 and 4.0.1.
Kamailio crash when module topoh module is loaded and removing Via headers in reply route with remove_hf("Via"); command.
Here is the backtrace:
Program received signal SIGSEGV, Segmentation fault.
th_del_via_cookie (msg=0x7fffffffd620, via=0x0) at th_msg.c:970
970 for(p=via->param_lst; p; p=p->next)
Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.107.el6.x86_64 pcre-7.8-6.el6.x86_64
(gdb)
(gdb) bt
#0 th_del_via_cookie (msg=0x7fffffffd620, via=0x0) at th_msg.c:970
#1 0x00007ffff32b70c4 in th_del_cookie (msg=0x7fffffffd620) at th_msg.c:991
#2 0x00007ffff32bea7e in th_msg_sent (data=0x7fffffffdd70) at topoh_mod.c:347
#3 0x00007ffff60f93c6 in msg_send (rb=0x7ffff15240d0, buf=0x7ffff7283a20, len=<value optimized out>) at ../../forward.h:141
#4 send_pr_buffer (rb=0x7ffff15240d0, buf=0x7ffff7283a20, len=<value optimized out>) at t_funcs.c:102
#5 0x00007ffff6130d90 in relay_reply (t=<value optimized out>, p_msg=<value optimized out>, branch=0, msg_status=200, cancel_data=0x7fffffffe110, do_put_on_wait=1) at t_reply.c:1877
#6 0x00007ffff61333e6 in reply_received (p_msg=0x7ffff7296270) at t_reply.c:2370
#7 0x00000000004547f5 in do_forward_reply (msg=0x7ffff7296270, mode=<value optimized out>) at forward.c:799
#8 0x000000000049a5ba in receive_msg (buf=<value optimized out>, len=1251, rcv_info=0x7fffffffe3a0) at receive.c:270
#9 0x00000000005281a6 in udp_rcv_loop () at udp_server.c:544
#10 0x0000000000464d3a in main_loop () at main.c:1638
#11 0x0000000000467a6c in main (argc=<value optimized out>, argv=<value optimized out>) at main.c:2566
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=300
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.