22 Sep
2015
22 Sep
'15
10:13 a.m.
On 22/09/15 08:40, Daniel-Constantin Mierla wrote:
On 22/09/15 07:17, Juha Heinanen wrote:
I was able to start with qmalloc and domain module using the default
config file:
./kamailio -f etc/kamailio.cfg -A WITH_SRCPATH -A WITH_MYSQL -A
WITH_MULTIDOMAIN -a no -E -e -ddd -x qm
Domain table has two records:
+----+-----------+------+---------------------+
| id | domain | did | last_modified |
+----+-----------+------+---------------------+
| 1 | test.com | abc | 2015-09-22 09:08:42 |
| 2 | test2.com | xyz | 2015-09-22 09:08:55 |
+----+-----------+------+---------------------+
If you get a coredump when using -x qm, send the backtrace.
Daniel
Daniel-Constantin Mierla writes:
Did you get a core for this one? There might be an issue inside domain
module...
Can you try building with MEMDBG=1, then add
'-x qm' to command line
starting kamailio? Let's see if q_malloc gets more hints.
does not start with
-x qm:
Sep 22 08:15:33 lohi /usr/bin/sip-proxy[19391]: : <core> [mem/q_malloc.c:446]:
qm_free(): BUG: qm_free: bad pointer 0x7f6e2aa6ab31 (out of memory block!) called from
domain: hash.c: hash_table_free(230) - aborting
Sep 22 08:15:33 lohi kernel: [116650.296517] sip-proxy[19391]: segfault at f0f0f0f0 ip
00007f6e22b1eb46 sp 00007fff2f809b10 error 4 in domain.so[7f6e22b10000+17000]