that pretty much answered most of my questions regarding the size of the memory chunks, but unfortunately not the reason of the crashing after 40k calls. MEMDBG doesn't report leaks on my module after finalizing Kamailio.
I don't see why the size should be changed since the values that I'm passing are always equal to 27 in length. Why is this?
After trying memory dumping with sercmd and killall, I ended up using pkg_sums() before and after every block of dynamic memory allocation. What I found out (and scared me) is that my module finishes with no leak according to the memory summary but, somehow, the memory consumption grows in, what appears to be, a linear basis.
Below the outputs per stage after the entry point function is called:
In the final stage, the module is supposed to store a SIPURI and return. That SIPURI will later be consulted by the script using a PV, reason why, stage 2 ends with 28 bytes of memory usage.
Later when the script tries to write to a PV, the function in charge is called and if the value is assigned (str.s != NULL) it frees the internal variable first and then does another pkg_str_dup().
Why pkg_malloc always gives 28 bytes instead of the 27 requested? Why the returned size is equal to 32 instead of just 27 in the last example? Can this be a memory fragmentation problem?
This happened after a few calls. Can this be the cause for a crash after running 40k calls?
I'm using kamailio 3.2.3.
Regards and thanks in advance.
Carlos
On Mon, Sep 10, 2012 at 12:18 PM, Daniel-Constantin Mierla <miconda@gmail.com> wrote:
Hello,
On 9/10/12 2:33 PM, Carlos Ruiz Díaz
wrote:
Hi Daniel,
no, it's just a plain make && make install.
I spent a few hours on debugging and I figured out that it
was an off by one error on a memcpy() on certain exceptional
conditions. I fixed that but then I found a memory leak that's
causing the crash after 40k calls but I'm having a hard time
interpreting the dump provided after sending the SIGUSR1 to the
process. if I'm not mistaken, there are two pkg_str_dup() leaks
per call but I'm still searching where I'm missing the
pkg_free().
Is there a way to know where in the code the pkg_str_dup was
called?
I tried with valgrind too, but after the macro expansion of
the memory management functions, is very hard to find where it
was called.
and cfgutils module readme for some functions that can be used in
config to dump the memory usage.
Cheers,
Daniel
Regards.
Carlos.
On Mon, Sep 10, 2012 at 4:02 AM,
Daniel-Constantin Mierla <miconda@gmail.com> wrote:
Hello,
yes, by default is with debug symbols on. Do you provide
special flags or parameters to the make command?
Cheers,
Daniel
On 9/8/12 9:39 PM, Carlos Ruiz Díaz wrote:
Hello list,
I'm trying to debug my module after it crashed
by SIGSEGV, but the problem is that I'm unable to
see the relevant data in the core file that's
being dumped after the crash.
For example, if I do bt full, I get:
0 0x0ef0f494 in append_string () from
/opt/install/kamailio-3.2.3/lib/kamailio/modules_k/cnx3a.so
No symbol table info available.
#1 0x0eef9658 in build_message () from
/opt/install/kamailio-3.2.3/lib/kamailio/modules_k/cnx3a.so
No symbol table info available.
Backtrace stopped: frame did not save the PC
Only the functions that were called but no
parameter values.
AFAIK, if I compile kamailio from sources, it
is by default compiled with the -g option, so, it
looks like that I'm missing something else.