Re: tracking down reference counting memory leaks

On Tuesday 21 of October 2014, Noel Grandin wrote:
> On 2014-10-20 06:27 PM, Michael Stahl wrote:
> > there are 2 ways i've tried to track down the 2 leaking acquire()s:
> >
> > 1. instrument the acquire()/release() method and run the test in gdb,
> > the script just takes 2 minutes to run (90 seconds of which are spent in
> > a single regex) but unfortunately printing 4000 stack traces with gdb
> > takes > 3 hours on my laptop; probably that can be sped up by disabling
>
> The backtrace API in GLIBC would speed this up considerably
> http://www.gnu.org/software/libc/manual/html_node/Backtraces.html

 Sadly, it'd also break it considerably. Unless that has improved recently 
(which I doubt), things like hidden symbol visibility make these functions 
practically useless.

-- 
 Lubos Lunak
 l.lunak@collabora.com