THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#442 - crash when using append_body_part()
User who did this - Daniel-Constantin Mierla (miconda)
----------
Is this the latest dev version with your code for multi part body?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=442#comment1512
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#440 - CRASH: segmentation fault if there is no dispatcher available
User who did this - Daniel-Constantin Mierla (miconda)
----------
Are the two file attached extracted from the same core file? There seems not to be a match on some variables.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=440#comment1511
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 - Víctor Seva (linuxmaniac)
Attached to Project - sip-router
Summary - crash when using append_body_part()
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 - Kamailio crashes with this silly test scenario
----
1(13819) DEBUG: tm [t_reply.c:728]: _reply_light(): DEBUG: reply sent out. buf=0x7fa95c6ed130: SIP/2.0 100 trying -..., shmem=0x7fa957170150: SIP/2.0 100 trying -
1(13819) DEBUG: tm [t_reply.c:738]: _reply_light(): DEBUG: _reply_light: finished
1(13819) ERROR: *** cfgtrace: c=[/code/tmp/kamailio_dump.cfg] l=913 a=25 n=xdbg
1(13819) DEBUG: <script>: new branch [0] to sip:service@127.0.0.1:5060
1(13819) ERROR: *** cfgtrace: c=[/code/tmp/kamailio_dump.cfg] l=914 a=5 n=route
1(13819) ERROR: *** cfgtrace: c=[/code/tmp/kamailio_dump.cfg] l=806 a=2 n=return
1(13819) DEBUG: <core> [msg_translator.c:1763]: get_boundary(): boundary is <--ub-dialogic-sw-1>
1(13819) DEBUG: <core> [msg_translator.c:1880]: check_boundaries(): last bondary without -- at the end
1(13819) DEBUG: <core> [msg_translator.c:1684]: replace_body(): old size body[522] actual[522]
1(13819) : <core> [data_lump.c:476]: free_lump(): BUG: free_lump: called on a not free-able lump:0x7fa95c6b1860 flags=1
0(13818) ALERT: <core> [main.c:776]: handle_sigs(): child process 13819 exited by a signal 6
----
The problem seems to be here[msg_translator.c:1690]:
del_nonshm_lump( &(msg->body_lumps) );
One or more files have been attached.
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=442
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#441 - route name in action struct
User who did this - Daniel-Constantin Mierla (miconda)
----------
There is no need to add a '\0' to the static values like:
default_routename="DEFAULT_ROUTE\0"
It can be simply:
default_routename="DEFAULT_ROUTE"
Ending zero is implicit in such cases.
Otherwise I am wondering if shouldn't be made to print with route type, like:
route[X] ...
failure_route[Y] ...
>From my understanding, now is printing:
r=[X] ...
r=[Y] ...
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=441#comment1510
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#439 - CRASH: segmentation fault after INVITE
User who did this - Nuno Miguel Reis (nmreis)
----------
Hi Daniel.
Please find the log attached.
----------
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=439#comment1509
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#440 - CRASH: segmentation fault if there is no dispatcher available
User who did this - Nuno Miguel Reis (nmreis)
----------
Hi Daniel.
Please find attached the requested output.
What i meant with no dispatcher available was this:
kamailio is in front of 2 freeswitch boxes configured in dispatcher. If i start kamailio without a running freeswitch instance i usually have a segmentation fault in kamailio like the one reported here.
----------
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=440#comment1508
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,
I am not sure if there is a better venue for posting this report, so
I'll post it here.
I'm running mediaproxy-ng
master:cb6990e43864b077dd6a24acfbdf5ef76c1a427e (4 April 2014), pre
rtpengine and all that. It crashed yesterday, with an estimated 700
concurrent calls running.
Core dump says:
(gdb) where
#0 monologue_offer_answer (monologue=0x0, streams=0x7f5bbff464c0, flags=
0x7f5bbff46430) at call.c:1711
#1 0x000000000041e160 in call_offer_answer_ng (input=<value optimized
out>, m=
0x1c19800, output=0x7f5ba00c3c18, opmode=<value optimized out>)
at call_interfaces.c:534
#2 0x0000000000414bdc in control_ng_incoming (obj=0x1c1c830,
buf=<value optimized out>, sin=0x7f5bbff56700, addr=
0x7f5bbff566c0 "xxx.xxx.xxx.xxx:37956") at control_ng.c:115
#3 0x00000000004140ce in udp_listener_incoming (fd=6, p=0x1c1ba70,
x=<value optimized out>) at udp_listener.c:52
#4 0x00000000004094be in poller_poll (p=0x1c179b0,
timeout=<value optimized out>) at poller.c:354
#5 0x000000000040710d in poller_loop (d=0x1c179b0) at main.c:522
#6 0x000000000040a1cf in thread_detach_func (d=0x1c142b0) at aux.c:160
#7 0x000000304e6079d1 in start_thread () from /lib64/libpthread.so.0
#8 0x000000304e2e8b6d in clone () from /lib64/libc.so.6
That's all I've got, and I highly, highly doubt I can reproduce this.
It's just something that happened after a certain amount of operation.
Any insights would be appreciated. Thanks!
-- Alex
--
Alex Balashov - Principal
Evariste Systems LLC
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
Please be kind to the English language:
http://www.entrepreneur.com/article/232906
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#441 - route name in action struct
User who did this - Víctor Seva (linuxmaniac)
----------
Initial work.
debug output:
------------------
3(11356) DEBUG: <core> [receive.c:193]: receive_msg(): preparing to run routing scripts...
3(11356) DEBUG: sl [sl_funcs.c:412]: sl_filter_ACK(): DEBUG : sl_filter_ACK: to late to be a local ACK!
3(11356) ERROR: *** cfgtrace:r=[DEFAULT_ROUTE] c=[/code/kamailio.cfg] l=465 a=63 n=assign
3(11356) ERROR: *** cfgtrace:r=[DEFAULT_ROUTE] c=[/code/kamailio.cfg] l=466 a=5 n=route
3(11356) ERROR: *** cfgtrace:r=[TEST1] c=[/code/kamailio.cfg] l=962 a=63 n=assign
3(11356) ERROR: *** cfgtrace:r=[TEST1] c=[/code/kamailio.cfg] l=963 a=2 n=return
3(11356) ERROR: *** cfgtrace:r=[DEFAULT_ROUTE] c=[/code/kamailio.cfg] l=467 a=5 n=route
3(11356) ERROR: *** cfgtrace:r=[TEST2] c=[/code/kamailio.cfg] l=967 a=63 n=assign
3(11356) ERROR: *** cfgtrace:r=[TEST2] c=[/code/kamailio.cfg] l=968 a=2 n=return
3(11356) ERROR: *** cfgtrace:r=[DEFAULT_ROUTE] c=[/code/kamailio.cfg] l=468 a=63 n=assign
3(11356) ERROR: *** cfgtrace:r=[DEFAULT_ROUTE] c=[/code/kamailio.cfg] l=471 a=5 n=route
3(11356) ERROR: *** cfgtrace:r=[REQINIT] c=[/code/kamailio.cfg] l=582 a=16 n=if
3(11356) ERROR: *** cfgtrace:r=[REQINIT] c=[/code/kamailio.cfg] l=577 a=25 n=mf_process_maxfwd_header
----------
One or more files have been attached.
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=441#comment1507
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 - Víctor Seva (linuxmaniac)
Attached to Project - sip-router
Summary - route name in action struct
Task Type - Feature Request
Category - Core
Status - New
Assigned To - Víctor Seva
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Now we have no info of the route in the action struct.
It will be nice to be able to know the route name where the action is.
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=441
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.