http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45827
--- Comment #28 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2010-10-24 18:56:49 UTC --- There is a quality of implementation issue going on here. Our goal has always been "zero" leaks. The reason? These errors can and do mask other things going on. This to me looks like some pointers are being whacked. maybe previously allocated space being reused that should not be. At this point no-one knows. ==4891== LEAK SUMMARY: ==4891== definitely lost: 33,500 bytes in 230 blocks ==4891== indirectly lost: 3,056 bytes in 150 blocks ==4891== possibly lost: 0 bytes in 0 blocks ==4891== still reachable: 320,546 bytes in 1,341 blocks ==4891== suppressed: 0 bytes in 0 blocks ==4891== Reachable blocks (those to which a pointer was found) are not shown. ==4891== To see them, rerun with: --leak-check=full --show-reachable=yes ==4891== ==4891== For counts of detected and suppressed errors, rerun with: -v ==4891== ERROR SUMMARY: 20 errors from 20 contexts (suppressed: 6 from 6)
