[sr-dev] [tracker] Task opened: segfault on loading dialplan module 3.1.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Bayan (bayan) Attached to Project - sip-router Summary - segfault on loading dialplan module 3.1.1 Task Type - Bug Report Category - Module Status - Unconfirmed Assigned To - Operating System - Linux Severity - High Priority - Normal Reported Version - 3.1 Due in Version - Undecided Due Date - Undecided Details - Version 3.1.1 segfaults on loading dialplan when loading a row with match_op 1. When the match mode was changed to 0 it works To isolate the bug we loaded kamailio dialplan module with the very simple match_op 1 regex row in the database (Postgres) and took a backtrace of the segfault. # select * from coreout_dialplan; id | dpid | pr | match_op | match_exp | match_len | subst_exp | repl_exp | attrs -----+------+----+----------+-----------+-----------+-----------+----------+------- 482 | 100 | 1 | 1 | ^201$ | 0 | | NJ | Backtrace is below: Program terminated with signal 11, Segmentation fault. #0 0x00007f435151e5da in build_rule (values=0x0) at dp_db.c:388 388 GET_STR_VALUE(repl_exp, values, 6); (gdb) bt #0 0x00007f435151e5da in build_rule (values=0x0) at dp_db.c:388 #1 0x00007f435151fb1f in dp_load_db () at dp_db.c:261 #2 0x00007f4351520182 in init_db_data () at dp_db.c:110 #3 0x00007f43515205f5 in init_data () at dp_db.c:176 #4 0x00007f435151b15d in mod_init () at dialplan.c:189 #5 0x00000000004db076 in init_mod (m=0x8fb170) at sr_module.c:872 #6 0x00000000004daff4 in init_mod (m=0x8fb570) at sr_module.c:869 #7 0x00000000004dc022 in init_modules () at sr_module.c:899 #8 0x0000000000463ec9 in main (argc=5845616, argv=0x7fff86a4ac18) at main.c:2339 (gdb) p repl_exp $1 = {s = 0x4 <Address 0x4 out of bounds>, len = 1366451880} (gdb) p values $2 = (db_val_t *) 0x0 More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=109 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.