http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53646
--- Comment #21 from Michael Matz <matz at gcc dot gnu.org> 2012-06-21 15:32:07 UTC --- (In reply to comment #20) > certainty. But it wouldn't have helped me that much further. I still would > have had to find out which functions were causing the wild write in order > to say with confidence that this is really the cause for the problem, and > not something like a normal program error. To expand on that: I had to do so because this particular std::list isn't part of any external API of the libraries in question, it's not passed around or returned, it's purely an internal implementation detail. Our wiki page makes it sound as if only using the problematic types in the external API is an issue. That is not the case, it's already just _using_ these types that's problematic.
