Re: fixing memory leaks before the pretest (was: Update on the Emacs release schedule?)

[Carsten Mattner <carstenmattner@googlemail.com>]

2012/1/7 Ted Zlatanov <tzz@lifelogs.com>:
> On Sat, 07 Jan 2012 15:10:38 +0800 Chong Yidong <cyd@gnu.org> wrote:
>
> CY> As for the code, there are still a number of issues that need more
> CY> attention, most prominently the mysterious memory leak(s) that may or
> CY> may not involve Gnus and/or GnuTLS and/or Mac OS X.
>
> I am seeing memory growth on GNU/Linux with Gnus and GnuTLS that I don't
> see otherwise without Gnus, so it's faintly possible GnuTLS is not the
> determining factor.  I have gone over the gnutls.c code and don't see
> where the GnuTLS glue could be leaking.  If it is, I'll need a tool like
> Valgrind to help me, and last time I tried that, the reports were not
> helpful to me (too much data, not enough leading back to GnuTLS).  I
> spent 2 days on this last week and meant to bring it up this week,
> actually (the discussion about GnuTLS on W32 sort of distracted me :)
>
> Maybe someone who actually knows how to use Valgrind could help me or
> try to find the leaks themselves?

Tried LLVM AddressSanitizer? It's supposed to be a low-impact compile flag.
http://clang.llvm.org/docs/AddressSanitizer.html
From the documentation I'm not sure it's useful for finding leaks.