[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: valgrind warnings
From: |
Paul Eggert |
Subject: |
Re: valgrind warnings |
Date: |
Fri, 04 Nov 2011 08:50:10 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 |
On 11/04/11 05:51, Dan Nicolaescu wrote:
> What should we do about this?
There's nothing wrong with the code; this is a false
alarm of valgrind, which is inherent to the way a
conservative garbage collector works.
One way to work around this valgrind issue is to supply
a suppression file, e.g., put something like the
following into a new file emacs/src/valgrind.supp:
{
Conservative garbage collection Cond
Memcheck:Cond
...
fun:mark_maybe_*
}
{
Conservative garbage collection Value8
Memcheck:Value8
...
fun:mark_maybe_*
}
(this is just an indication of what it would look
like; more is needed). The goal is to suppress
false positives while minimizing false negatives.
- Re: valgrind warnings [Re: Emacs bzr memory footprint], Dan Nicolaescu, 2011/11/04
- Re: valgrind warnings [Re: Emacs bzr memory footprint], Andreas Schwab, 2011/11/04
- Re: valgrind warnings,
Paul Eggert <=
- Re: valgrind warnings [Re: Emacs bzr memory footprint], Stefan Monnier, 2011/11/04
- Re: valgrind warnings [Re: Emacs bzr memory footprint], Dan Nicolaescu, 2011/11/04
- Re: valgrind warnings [Re: Emacs bzr memory footprint], Paul Eggert, 2011/11/04
- Re: valgrind warnings [Re: Emacs bzr memory footprint], Dan Nicolaescu, 2011/11/05
- Re: valgrind warnings [Re: Emacs bzr memory footprint], Paul Eggert, 2011/11/05
- Re: valgrind warnings [Re: Emacs bzr memory footprint], Dan Nicolaescu, 2011/11/06
- Re: valgrind warnings [Re: Emacs bzr memory footprint], Paul Eggert, 2011/11/06