This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/29529] purify with iostream reports 128 uninitialized memory reads
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Oct 2006 04:22:15 -0000
- Subject: [Bug libstdc++/29529] purify with iostream reports 128 uninitialized memory reads
- References: <bug-29529-2948@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from pcarlini at suse dot de 2006-10-26 04:22 -------
(In reply to comment #2)
> I just tried valgrind. I'm not really familiar with valgrind, but as far
> as I can tell it reports no problems. So, either purify is wrong, valgrind
> is wrong, or they're both wrong in different ways.
Maybe "wrong" is too strong a statement, in this case. In practice, what often
makes a difference is that valgrind knows about many details of the GNU
environment (for instance about the underlying glibc) and is thus able to
automatically filter out many potential false positives. It does that via a
constantly updated so-called suppression file (see the manual, about that).
Anyway, I will double check myself in a few days...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29529