[sr-dev] [tracker] Task opened: Bug in tm with topoh modules - segfault on callid comparison.

sip-router bugtracker at sip-router.org
Mon Feb 3 12:17:52 CET 2014


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Nick Altmann (nikbyte) 

Attached to Project - sip-router
Summary - Bug in tm with topoh modules - segfault on callid comparison.
Task Type - Bug Report
Category - tm
Status - Unconfirmed
Assigned To - 
Operating System - Linux
Severity - High
Priority - Normal
Reported Version - 4.1
Due in Version - Undecided
Due Date - Undecided
Details - Bug in tm with topoh modules.
Sometimes I see in log:
 0(30156) ERROR: topoh [th_mask.c:166]: th_mask_decode(): invalid input string"1b0ba56b55c2286d-30157 at 127.0.0.1"
 0(30156) ERROR: topoh [th_msg.c:480]: th_unmask_callid(): cannot decode callid
and then segfault.

#0  0x00007f8ad98aac6b in t_reply_matching (p_msg=0x7f8adaca2f20, p_branch=0x7fff352a8380) at t_lookup.c:987
#1  0x00007f8ad98ac43c in t_check_msg (p_msg=0x7f8adaca2f20, param_branch=0x7fff352a8380) at t_lookup.c:1129
#2  0x00007f8ad98ac917 in t_check (p_msg=0x7f8adaca2f20, param_branch=0x7fff352a8380) at t_lookup.c:1171
#3  0x00007f8ad98ca196 in reply_received (p_msg=0x7f8adaca2f20) at t_reply.c:2188

(gdb) f 0
#0  0x00007f8ad98aac6b in t_reply_matching (p_msg=0x7f8adaca2f20, p_branch=0x7fff352a8380) at t_lookup.c:987
987			        (p_msg->callid->body.len != p_cell->uas.request->callid->body.len ||
(gdb) p *p_msg->callid
$2 = {type = HDR_CALLID_T, name = {s = 0x9236f3 "Call-ID: 1b0ba56b55c2286d-30157 at 127.0.0.1\r\nContent-Length: 0\r\nTH: uch\r\n\r\n",
    len = 7}, body = {s = 0x9236fc "1b0ba56b55c2286d-30157 at 127.0.0.1\r\nContent-Length: 0\r\nTH: uch\r\n\r\n", len = 32}, len = 43,
  parsed = 0x0, next = 0x0}
(gdb) p *p_cell->uas.request
Cannot access memory at address 0x0


More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=390

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