------- Comment #5 from reichelt at gcc dot gnu dot org 2008-04-10 06:16 ------- I can still reproduce it with trunk, 4.3 branch and 4.2 branch from 2008-04-07. I can't reproduce it on x86_64, though (no segfault, no valgrind error).
Did you try adding random characters before %:%: ? Maybe this changes memory layout so much that you see the segfault, too. Concerning comment #3: I cannot imagine that pfile->buffer was 0 from the beginning. It looks as if something trampled on the memory later. (I'd have to check that, though.) That would also explain the totally different error in the original report (and why you don't run into trouble with the same testcase). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35326
