[Bug libstdc++/29529] purify with iostream reports 128 uninitialized memory reads
--- Comment #4 from pcarlini at suse dot de 2006-10-28 22:34 --- Ok, I have double checked that both on 4.0.3 and the active branches everything is fine per Valgrind (3.2.1). You may want to pass -v to Valgrind and look at the supp: lines in the output, showing the used suppressions: interestingly, one pretty commonly used is called Ubuntu-stripped-ld.so, that is, it has been added to cope with Ubuntu-specific false positives... -- pcarlini at suse dot de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29529
[Bug libstdc++/29529] purify with iostream reports 128 uninitialized memory reads
--- Comment #2 from mstaley at lanl dot gov 2006-10-25 22:38 --- (In reply to comment #1) This is most likely a purify problem. Have you tried using valgrind instead? 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. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29529
[Bug libstdc++/29529] purify with iostream reports 128 uninitialized memory reads
--- 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
[Bug libstdc++/29529] purify with iostream reports 128 uninitialized memory reads
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-10-20 21:34 --- This is most likely a purify problem. Have you tried using valgrind instead? -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Component|c++ |libstdc++ http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29529
