FS#42299 - [gcc] internal compiler error: Segmentation fault while building WebKit through jhbuild

Attached to Project: Arch Linux
Opened by Fabien Bourigault (fbourigault) - Wednesday, 08 October 2014, 10:08 GMT
Last edited by Allan McRae (Allan) - Saturday, 18 October 2014, 23:02 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When I'm building WebKit (webkitgtk) through jhbuild, I get the following error :

In file included from /usr/include/c++/4.9.1/functional:55:0,
from /usr/include/c++/4.9.1/memory:79,
from /home/fabien/Projets/jhbuild/webkitgtk-2.6.0/Source/WTF/wtf/StdLibExtras.h:31,
from /home/fabien/Projets/jhbuild/webkitgtk-2.6.0/Source/WTF/wtf/FastMalloc.h:27,
from /home/fabien/Projets/jhbuild/webkitgtk-2.6.0/Source/JavaScriptCore/config.h:56,
from /home/fabien/Projets/jhbuild/webkitgtk-2.6.0/Source/JavaScriptCore/dfg/DFGDriver.cpp:26:
/usr/include/c++/4.9.1/tuple: In instantiation of 'class std::tuple<JSC::CallEdgeLog*, std::default_delete<JSC::CallEdgeLog> >':
/usr/include/c++/4.9.1/bits/unique_ptr.h:147:57: required from 'class std::unique_ptr<JSC::CallEdgeLog>'
/home/fabien/Projets/jhbuild/webkitgtk-2.6.0/Source/JavaScriptCore/runtime/VM.h:238:34: required from here
/usr/include/c++/4.9.1/tuple:594:2: internal compiler error: Segmentation fault
tuple(allocator_arg_t __tag, const _Alloc& __a,
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.

If I re-run the build it sometime fails at a different location. This happens when building WebKit 2.6.0.

This only happens randomly while building gtk+ through jhbuild. But in this case, If I re-run the build it succeed.
   webkitgtk-gcc-segfault.txt (92.7 KiB)
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 18 October 2014, 23:02 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Random segfaults are not a gcc issue.
Comment by Jan de Groot (JGC) - Wednesday, 08 October 2014, 10:33 GMT
If these segmentation faults are at random places, I would suggest testing your system memory with memtest86+.
Comment by Fabien Bourigault (fbourigault) - Wednesday, 08 October 2014, 11:14 GMT
I will next night.

Loading...