This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/53615] Buffer overflow in the compiler?
- From: "gjl at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 02 Aug 2012 16:45:24 +0000
- Subject: [Bug other/53615] Buffer overflow in the compiler?
- Auto-submitted: auto-generated
- References: <bug-53615-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53615
--- Comment #7 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2012-08-02 16:45:24 UTC ---
(In reply to comment #6)
> You should run the compiler under Valgrind and see whether it complains.
I never built the compiler with valgrind support. Is the a comprehensible
documentation?
The wiki has http://gcc.gnu.org/wiki/DebuggingGCC to use valgring as wrapper,
but I also see many valgrind strings in GCC sources and some in gcc/doc.
You mean --enable-checking=valgrind?
This bug does no more appear since PR53595 is fixed. This is strange; maybe
it's just incidental and now some other test case is needed to trigger this
bug.
Or one bug is actually a duplicate if the other?