------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-18 14:33 ------- (In reply to comment #4) > That's strange. I thought ggc_free should poison the memory that is > freed if the compiler is built with checking enabled. So anything > that uses it after the ggc_free should segfault or die in a similar > horrible way. > > Did someone remove ENABLE_GC_CHECKING from --enable-checking??
No, we do poison it but since this is only a read we don't get any diagnostic unless you use valgrind because we poison it even further with valgrind and say the memory is useless. Mark thought his patch was safe and he even tried to explain why he thought it was safe but this is the second bug which was effected by it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19349
