[sr-dev] [tracker] Task opened: Crash in topoh module when To header missing

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Michel de Weerd (mweerd) Attached to Project - sip-router Summary - Crash in topoh module when To header missing Task Type - Bug Report Category - Module Status - Unconfirmed Assigned To - Operating System - Linux Severity - Medium Priority - Normal Reported Version - 4.0 Due in Version - Undecided Due Date - Undecided Details - Testing with tool https://www.ee.oulu.fi/research/ouspg/PROTOS_Test-Suite_c07-sip reveals a problem in the topoh module, testscenario 1243 java -jar c07-sip-r2.jar -lport 10000 -dport 4060 -touri test(a)10.38.102.50 -start 1243 -stop 1243 When the To header is mising in the request the topoh crashes with the following backtrace: warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff8867000 Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio.pid -m 64 -M 4 -u kamailio -g kam'. Program terminated with signal 11, Segmentation fault. #0 0x00002b58c950870b in th_msg_received (data=<value optimized out>) at topoh_mod.c:262 262 if(dialog) (gdb) bt #0 0x00002b58c950870b in th_msg_received (data=<value optimized out>) at topoh_mod.c:262 #1 0x00000000004a6de4 in receive_msg () #2 0x000000000053e22b in udp_rcv_loop () #3 0x0000000000470af5 in main_loop () #4 0x0000000000474898 in main () The SIP request to kamailio contains the following SIP data: INVITE sip:test@10.38.102.50 SIP/2.0 Via: SIP/2.0/UDP mdw:10000;branch=z9hG4bK000012430 From: 1243 <sip:user@mdw>;tag=1243 : Receiver <sip:test@10.38.102.50> Call-ID: 0@mdw CSeq: 1 INVITE Contact: 1243 <sip:user@mdw> Expires: 1200 Max-Forwards: 70 Content-Type: application/sdp Content-Length: 122 v=0 o=1243 1243 1243 IN IP4 mdw s=Session SDP c=IN IP4 127.0.1.1 t=0 0 m=audio 9876 RTP/AVP 0 a=rtpmap:0 PCMU/8000 More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=303 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.