Re: [SR-Users] Segfault in Kamailio 1-3-4 to 1.5.5

On 03/01/2011 11:02 AM, Andrew O. Zhukov wrote: Hello, I had been checking the coredumps you provided for a while. I don't think they are very useful because for me this looks like an Heisenbug. The coredumps only show the result of the memory corruption and not the cause. Daniel has asked you for some input when compiling with memory debug on (to see if canary values where overwritten by what operations). I have not seen this output yet (don't know if you send it privately to him, or I have missed it on the list). Try to compile again with debug memory support, and set logging to a apropriate level. An idea is to set a special server with a special version of Kamailio. Minimize the number of children (use only one worker) and use just part of the traffic so you have a easier debugging. The bug affects private memory so the number of children should not be an impact. Also you might want to increase the PKG_MEM_SIZE from the default value of 4 MB to something bigger (try 10-15 MB or more). See if this has an impact on the bug (it might be caused by fragmentation in this case a bigger pool might help). If all else fail, I strongly suggest dropping pkg_malloc all together, and using libc's Malloc() instead. This is done at compile time by removing the -DPKG_MALLOC from Makefile.defs and recompiling.. This should fix your bug Marius