[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: valgrind warnings [Re: Emacs bzr memory footprint]
From: |
Florian Weimer |
Subject: |
Re: valgrind warnings [Re: Emacs bzr memory footprint] |
Date: |
Sun, 04 Dec 2011 22:11:47 +0100 |
* Ted Zlatanov:
> On Fri, 28 Oct 2011 07:52:12 -0400 Dan Nicolaescu <address@hidden> wrote:
> DN> On Fedora 15 with valgrind-3.6.1 it is possible to run
>
> DN> valgrind ./temacs
>
> I ran this and opened and closed a GnuTLS connection many times:
>
> (open-gnutls-stream "tls" "tls-buffer" "imap.gmail.com" "imaps")
>
> I did not see any errors printed when I did this, but on exit a lot of
> information was printed that did not seem related (I could not analyze
> it all, it was too much data and I don't know what to look for other
> than "gnutls"). Is this enough to tell us there are no memory leaks in
> the "open connection" part of the code? I'll test sending and receiving
> data if so.
I think you need to run
valgrind --leak-check=yes ./temacs
and actually terminate the program to get the dump of leaked
resources.
Has the bug been identified in the meantime? I've got some very
long-running processes using GnuTLS which grow without bounds,
too---but I've been blaming this on bugs in my Perl wrapper. In that
cases, just opening and closing connections (and sending a bit of
data) does not trigger the leak condition, either.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: valgrind warnings [Re: Emacs bzr memory footprint],
Florian Weimer <=