Re: Memory leak in a shared library plugin

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Cason, Kenny" <kenny.cason@xxxxxxxxxx> writes:

>   3) does not run from the command line so use of gdb and breakpoints is of little value

See gdb's attach command.


> Determine why the memory continuously increases (memory leak?) for
> Daemon A. If it's a memory leak is it in Daemon A or Plugin B.

Tough problem.  I think I would modify the heap allocation and free
routines in the plugin to log a message.  Then with some scripting you
could perhaps see if all allocated memory was freed during a typical
plugin call.

Ian

[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux