44145 2010-08-17 17:36:01 -0700 [Qt] Internal compiler error with MinGW in Document.cpp 2010-08-18 09:58:31 -0700 1 1 1 Unclassified WebKit WebKit Qt 528+ (Nightly build) All Windows XP RESOLVED WONTFIX Qt P2 Normal --- 1 mihaip webkit-unassigned eric ossy oldest_to_newest 265870 0 mihaip 2010-08-17 17:36:01 -0700 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 265871 1 mihaip 2010-08-17 17:36:34 -0700 +Eric since James says he's interested in bot redness. 265911 2 eric 2010-08-17 19:37:53 -0700 The right place is to file a bug with gcc. :) 265941 3 mihaip 2010-08-17 22:08:01 -0700 (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. 265942 4 ossy 2010-08-17 22:14:15 -0700 (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. :( 266181 5 ossy 2010-08-18 09:58:31 -0700 Now clean build solved this problem. But I don't know how can we fix it, because it might be a flakey gcc bug ...