Can you set memdbg and memlog lower than debug and reproduce the case again? That results in logging all memory operations, as I need to know what part of code allocated previous fragment, because it does a overflow write, going over the head of next fragment, thus corrupting it structure.
All logs from start to stop are required in this case, so it can be quite big file. You can email directly to me or provide some temporary access to troubleshoot the system (if that is a more convenient option).
Cheers, Daniel
On 8/28/13 10:04 AM, Alex Balashov wrote:
On 08/28/2013 04:03 AM, Daniel-Constantin Mierla wrote:
Where are the log messages? They are important too.
The only log message I got from Kamailio itself was:
Aug 28 03:42:09 gw1 /usr/local/sbin/kamailio[7913]: : <core> [mem/q_malloc.c:159]: qm_debug_frag(): BUG: qm_*: prev. fragm. tail overwritten(3630643536313a64, 2d303634622d3965 [0x7f99b713d008:0x7f99b713d038]!