[sr-dev] [tracker] Task opened: crash when using append_body_part() (Attachment added)

sip-router bugtracker at sip-router.org
Mon Jun 9 11:38:46 CEST 2014


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 at 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.



More information about the sr-dev mailing list