db_new_result->pkg_malloc(qm_malloc)->qm_find_free, func qm_find_free
return 0, can not find mem when i close memdbg.
2014-10-20 18:57 GMT+08:00 张顺通 <shuntongzh...@gmail.com>:
> rhel5
> $cat /proc/cpuinfo | grep name | cut -f2 -d: | uniq -c
> 24 Intel(R) Xeon(R) CPU E5-2430 0 @ 2.20GHz
> rhel6
> cat /proc/cpuinfo | grep name | cut -f2 -d: | uniq -c
> 16 Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
>
> not Embedded device, normal server.
>
>
> gdb
>
> (gdb) f 2
> #2 0x0000000000615b74 in qm_debug_frag (qm=0x7ffff6c55010,
> f=0x7ffff6cdcf08) at mem/q_malloc.c:161
> 161 abort();
> (gdb) p *f
> $1 = {size = 7831720, u = {nxt_free = 0x7ffff6c893f8, is_free =
> 140737333728248}, file = 0x7ffff6a4c93d "db_mysql: km_my_con.c",
> func = 0x758307 "fragm. from qm_malloc", line = 62, check = 4042322160}
>
>
> 2014-10-20 18:30 GMT+08:00 Daniel-Constantin Mierla <mico...@gmail.com>:
>
>> physical machine is the same? Is it standard OS installation, or some
>> customizations (e.g. custom kernel modules, etc.)? Embedded device? What
>> CPU?
>>
>> Daniel
>>
>>
>> On 20/10/14 12:24, 张顺通 wrote:
>>
>> os is rhel.
>> rhel6 is ok, rhel5 can not start.
>>
>> 2014-10-20 18:11 GMT+08:00 Daniel-Constantin Mierla <mico...@gmail.com>:
>>
>>> What are the differences between the server that works and the one that
>>> doesn't? I mean hardware and operating system details?
>>>
>>> Checking quickly the source code and comparing with logs, it doesn't
>>> reveal any problem -- it is about allocation of the next fragment, which
>>> was not used at all before, after the one allocated previously. The only
>>> reason I can think of it right now is corrupted memory or faulty OS.
>>>
>>> Daniel
>>>
>>>
>>> On 20/10/14 11:56, 张顺通 wrote:
>>>
>>> 4.2 have the same problem.
>>> at begin i use 4.1, i think this is a bug in 4.1; then i use 4.2 to
>>> check to see if the problem is solved. problems still in.
>>>
>>> see ka_4_2_0.log
>>>
>>> ka_4_2_0.log
>>> <https://docs.google.com/file/d/0B5x1TDtoeVvAckdMbDRmT3E3UjA/edit?usp=drive_web>
>>>
>>>
>>> 2014-10-20 17:48 GMT+08:00 张顺通 <shuntongzh...@gmail.com>:
>>>
>>>> ka.log is genrate by kamailio 4.1.6.
>>>>
>>>> 2014-10-20 17:44 GMT+08:00 Daniel-Constantin Mierla <mico...@gmail.com>
>>>> :
>>>>
>>>>> Are you using 4.1 or 4.2?
>>>>>
>>>>> Because the subject mentioned 4.2 but the version of kamailio is 4.1
>>>>>
>>>>> Daniel
>>>>>
>>>>> On 20/10/14 11:39, 张顺通 wrote:
>>>>> > -M 12 can not help. all config is same.
>>>>> >
>>>>> > see ka.log in attachment, kamailio version is 4.1.6
>>>>> >
>>>>> > version: kamailio 4.1.6 (x86_64/linux) 010d57
>>>>> >
>>>>> > flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
>>>>> > DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
>>>>> > DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
>>>>> > USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
>>>>> >
>>>>> > ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
>>>>> > MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
>>>>> >
>>>>> > poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
>>>>> >
>>>>> > id: 010d57
>>>>> >
>>>>> > compiled on 16:48:03 Oct 20 2014 with gcc 4.1.2
>>>>> >
>>>>> >
>>>>>
>>>>> --
>>>>> Daniel-Constantin Mierla
>>>>> http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
>>>>>
>>>>>
>>>>
>>>
>>> --
>>> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
>>> http://www.linkedin.com/in/miconda
>>>
>>>
>>
>> --
>> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
>> http://www.linkedin.com/in/miconda
>>
>>
>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
