Summary: | www-client/chromium-63.0.3239.132 ../../base/trace_event/trace_log.h:93:62: internal compiler error: Segmentation fault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mauro Maroni <mauro.maroni> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | gentoobugs.pistos, slyfox, toolchain |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
emerge -pqv '=www-client/chromium-63.0.3239.132::gentoo' environment `emerge --info '=www-client/chromium-63.0.3239.132::gentoo'` of Pistos `emerge -pqv '=www-client/chromium-63.0.3239.132::gentoo'` of Pistos /var/log/portage/www-client:chromium-63.0.3239.132:20180125-204411.log of Pistos `gcc -Q -O2 --help=optimizers --help=target` of Pistos |
Description
Mauro Maroni
2018-01-18 17:15:33 UTC
Created attachment 515266 [details]
build.log
Created attachment 515268 [details]
emerge -pqv '=www-client/chromium-63.0.3239.132::gentoo'
Created attachment 515270 [details]
environment
../../base/trace_event/trace_log.h:93:62: internal compiler error: Segmentation fault I would guess binutils or gcc is broken. Please try rebuilding them. Otherwise, please check dmesg for errors. (In reply to Mike Gilbert from comment #4) > ../../base/trace_event/trace_log.h:93:62: internal compiler error: > Segmentation fault > > I would guess binutils or gcc is broken. Please try rebuilding them. > > Otherwise, please check dmesg for errors. Rebuilt gcc yesterday, just rebuilt binutils. Same result. Nothing on dmesg. @toolchain: Can you give any tips to help Mauro troubleshoot this gcc segfault? You need to extract preprocessed file and exact options to gcc that crash it. For that you need to: - go to $WORKDIR and run failing gcc command with '-save-temps' added - find corresponding *.i* file - attach exact command and *.i* file - if you are using -march=native we need expanded form of it. Paste output of 'gcc -Q -O2 --help=optimizers --help=target' Then we can try to reproduce/explore it. Once reproduced I personally use c-reduce to shrink sample down to something tiny: http://trofi.github.io/posts/198-c-reduce-nano-howto.html I, too, cannot build this exact chromium version. Also getting segfaults, but a different one every time: # cat /var/log/portage/*chrom*2018012* | grep 'Segmentation fault' gen/ui/gfx/mojo/buffer_types.mojom-shared-internal.h:255:5: internal compiler error: Segmentation fault gen/blink/core/ComputedStyleBase.h:6657:5: internal compiler error: Segmentation fault ../../net/http/http_stream_factory_impl.h:139:49: internal compiler error: Segmentation fault /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:313:35: internal compiler error: Segmentation fault ../../third_party/WebKit/Source/platform/fonts/FontDescription.h:146:3: internal compiler error: Segmentation fault ../../third_party/WebKit/Source/core/html/custom/V0CustomElementUpgradeCandidateMap.h:61:41: internal compiler error: Segmentation fault ../../third_party/WebKit/Source/core/css/resolver/CSSPropertyPriority.h:59:1: internal compiler error: Segmentation fault ../../gpu/command_buffer/service/gles2_cmd_decoder.cc:10346:34: internal compiler error: Segmentation fault /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/include/g++-v6/bits/hashtable_policy.h:627:5: internal compiler error: Segmentation fault I have recently upgraded from profile 13 to profile 17, and upgraded gcc from 5.4 to 6.4. I (eventually) followed the instructions in the eselect news item, and the Upgrading GCC instructions, re: rebuilding gcc, libtool, and empty-tree world, etc. etc. Every other package in my @world [eventually] succeeded in building. chromium-63 is the final one that won't. I am attaching emerge --info, emerge -pqv, [one of] the full build log[s], and gcc -q. Created attachment 516744 [details]
`emerge --info '=www-client/chromium-63.0.3239.132::gentoo'` of Pistos
Created attachment 516746 [details]
`emerge -pqv '=www-client/chromium-63.0.3239.132::gentoo'` of Pistos
Created attachment 516748 [details]
/var/log/portage/www-client:chromium-63.0.3239.132:20180125-204411.log of Pistos
Created attachment 516750 [details]
`gcc -Q -O2 --help=optimizers --help=target` of Pistos
I scaled down from MAKEOPTS="-s -j5 -l 6" to MAKEOPTS="-s -j2 -l 3" and then it succeeded for me. Sorry for the noise! Hope my example helps someone else, though. For the record, my system has 12 GB RAM. Tried one more time with -j2 and this time it worked. I do not know, maybe it was a hardware issue. |