Bug 44145 – [Qt] Internal compiler error with MinGW in Document.cpp

• Status: RESOLVED
• Resolution: WONTFIX
• Component: WebKit Qt

[Mihai Parparita]

In theory this is http://trac.webkit.org/changeset/65573's fault, but that seems unlikely (it didn't touch that part of the code).

from http://build.webkit.org/builders/Qt%20Windows%2032-bit%20Release/builds/6205/steps/compile-webkit/logs/stdio:

..\..\..\WebCore\dom\Document.cpp: In member function 'void WebCore::Document::addElementById(const WTF::AtomicString&, WebCore::Element*)':
..\..\..\WebCore\dom\Document.cpp:1140:6: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make.exe[1]: *** [obj/release/Document.o] Error 1
make.exe[1]: *** Waiting for unfinished jobs....
make.exe[1]: Leaving directory `T:/WindowsRelease/buildslave/qt-windows-32bit-release/build/WebKitBuild/Release/WebCore'
make: *** [sub-WebCore-make_default-ordered] Error 2
program finished with exit code 2
elapsedTime=154.094000

[Mihai Parparita]

+Eric since James says he's interested in bot redness.

[Eric Seidel (no email)]

The right place is to file a bug with gcc. :)

[Mihai Parparita]

(In reply to comment #2)
> The right place is to file a bug with gcc. :)

I was under the impression that the Qt build uses a particularly old version of GCC in a less common environment (MinGW) and so the bug may not be present in more recent versions.

[Csaba Osztrogonác]

(In reply to comment #3)
> (In reply to comment #2)
> > The right place is to file a bug with gcc. :)
> 
> I was under the impression that the Qt build uses a particularly old version of GCC in a less common environment (MinGW) and so the bug may not be present in more recent versions.

Not at all, we ran into this bug more times earlyer with MinGW-4.4.
And then I updated to MinGW-4.5, but this bug occurs now and again.
Unfortunately we don't know what cause it, because sometimes a simple
clean build or a machine restart solve the problem, sometimes not. :(

[Csaba Osztrogonác]

Now clean build solved this problem.

But I don't know how can we fix it, because it might be a flakey gcc bug ...