# /usr/gcc-3.3/bin/gcc -M -O foo.c cc1: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions.
Created attachment 4986 [details] A testcase (foo.c) This is the bad input which causes gcc 3.3.2 to dump core.
Confirmed with 3.3.2-prerelease and 3.4. This is a regression from 3.2. The trigger is a missing ")" in a macro invokation.
From Phil's regression hunter: Search converges between 2002-06-02-trunk (#80) and 2002-07 -14-trunk (#81).
CPP maintainers -- Do any of you think this worth fixing in 3.3.x?
Yes, I do. I will look at this, but I would really appreciate a reduced testcase if possible.
I spent a little time chopping things out of the test case. It seems to be very sensitive to the size of the file. I gave up after chopping 20 KB out of the file. C:\Temp>gcc -M foo2.c cc1.exe: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.mingw.org/bugs.shtml> for instructions. C:\Temp>
Created attachment 5374 [details] Slightly reduced testcase
Mine.
Zack -- I'm going to make a pre-release within two days, do you think you'll have something ready by then? Thanks, -- Gaby
Subject: Re: [3.3/3.4/3.5 regression] Memory corruption in cpp on bad input Sorry, I've been concentrating on the c-decl.c mess in 3.4. zw
Adjust milestone
I cannot reproduce this problem in GCC 3.4.0. Is there a more reliable way of reproducing it? In any case, I'm retargeting this at 3.4.1. Gaby and I have already agreed that the 3.4.x target milestones take precedence over the 3.3.x milestones. Gaby, please note that this used to be marked as targeted at 3.3.4, but is now targeted at 3.4.1.
IIRC this one was fixed already...? Has nothing to do with the c-decl.c rewrite, just for the record.
Already fixed -- at least for me. Reopen if this still occurs.