Hi,
I posted previously on this issue but never got any replies.
Has anyone had this experience with 4.1?
It seems that as soon as a UAC tries to register, Kamailio segfaults:
May 20 09:41:00 vmhost /usr/sbin/kamailio[27806]: ALERT: <core>
[main.c:775]: handle_sigs(): child process 27813 exited by a signal 11
May 20 09:41:00 vmhost /usr/sbin/kamailio[27806]: ALERT: <core>
[main.c:778]: handle_sigs(): core was not generated
May 20 09:41:00 vmhost /usr/sbin/kamailio[27806]: INFO: <core>
[main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD
May 20 09:41:00 vmhost kernel: [251087.555502] kamailio[27813]: *segfault
at* 7fa5d1d0a1dc ip 0000000000536104 sp 00007fffaade6c20 error 4 in
kamailio[400000+27a000]
May 20 09:41:00 vmhost /usr/sbin/kamailio[27812]: INFO: <core>
[main.c:841]: sig_usr(): INFO: signal 15 received
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#432 - websocket and xmlrpc cause invalid increase of core:unsupported_methods stats
User who did this - Juha Heinanen (jh)
Reason for closing: Fixed
Additional comments about closing: closing due to "quick fix" by daniel.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=432
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#432 - websocket and xmlrpc cause invalid increase of core:unsupported_methods stats
User who did this - Daniel-Constantin Mierla (miconda)
----------
A quick fix would be to count only if protocol is SIP.
For later, would be good to parse these methods and keep internal id for faster comparison (then will become automatically recognized), but will require to review more parts of the code.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=432#comment1476
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 - Juha Heinanen (jh)
Attached to Project - sip-router
Summary - websocket and xmlrpc cause invalid increase of core:unsupported_methods stats
Task Type - Bug Report
Category - Core
Status - New
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - each xmlrpc request and websocket connection setup causes invalid increase of core:unsupported_methods stats.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=432
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#430 - bogus core statistics?
User who did this - Juha Heinanen (jh)
Reason for closing: Deferred
Additional comments about closing: i'm closing this item and will create a new one in order to simplify the issue.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=430
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,
some time ago it was proposed to use a code review tool to analyze
patches, the topic was also discussed during the last IRC devel meeting.
I cc-ed users mailing list, because people there might have experiences
with some of them.
I found on wikipedia a short list of available applications for this
purpose:
- http://en.wikipedia.org/wiki/List_of_tools_for_code_review
Personally I haven't used any so far. Iirc, gerrit was proposed before
by Victor Seva. From the wikipedia list, Differential would be
straightforward to deploy from dependencies point of view, as we have
php on our servers. But I have no clue which is the right/best to use,
so here we have to decide if worth to use one and which one.
Besides the above one, perhaps github has an integrated review tool. I
can be considered as an alternative as well.
My opinion is that such tool is useful, specially for big patches, to
allow easier more people to have a look at them.
Hoping to get feedback on benefits of such tools and which would be the
right/best to use.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda