public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Package compile failures with "internal compiler error: Segmentation fault".
Date: Wed, 4 Sep 2024 00:26:37 -0400	[thread overview]
Message-ID: <3b1883a6-cdf2-439b-b713-391e53a11d76@gentoo.org> (raw)
In-Reply-To: <8c26be16-d033-ea3f-06e1-a9ce84cbbafb@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2733 bytes --]

On 9/3/24 7:28 PM, Dale wrote:
> Howdy,
> 
> I was trying to re-emerge some packages.  The ones I was working on
> failed with "internal compiler error: Segmentation fault" or similar
> being the common reason for failing.  I did get gcc to compile and
> install.  But other packages are failing, but some are compiling just
> fine.  Here's a partial list at least. 
> 
> net-libs/webkit-gtk
> kde-plasma/kpipewire
> sys-devel/clang
> sys-devel/llvm




> /var/tmp/portage/net-libs/webkit-gtk-2.44.2/work/webkitgtk-2.44.2/Source/WebCore/platform/ScrollableArea.h:96:153:
> internal compiler error: in layout_decl, at stor-layout.cc:642
>    96 |     virtual bool requestScrollToPosition(const ScrollPosition&,
> const ScrollPositionChangeOptions& =
> ScrollPositionChangeOptions::createProgrammatic()) { return false; }
>      
> |                                                                                                                                                        
> ^
> 0x1d56132 internal_error(char const*, ...)
>         ???:0
> 0x6dd3d1 fancy_abort(char const*, int, char const*)
>         ???:0
> 0x769dc4 start_preparsed_function(tree_node*, tree_node*, int)
>         ???:0
> 0x85cd68 c_parse_file()
>         ???:0
> 0x955f41 c_common_parse_file()
>         ???:0




> /var/tmp/portage/sys-devel/clang-16.0.6/work/clang/lib/CodeGen/CodeGenModule.h:668:31:  
> required from here
> /usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/tuple:1810:43:
> internal compiler error: Segmentation fault
>  1810 |     { return std::__get_helper<__i>(__t); }
>       |                                           ^
> 0x1d56132 internal_error(char const*, ...)
>         ???:0
> 0x9816d6 ggc_set_mark(void const*)
>         ???:0
> 0x8cc377 gt_ggc_mx_lang_tree_node(void*)
>         ???:0
> 0x8cccfc gt_ggc_mx_lang_tree_node(void*)
>         ???:0
> 0x8ccddf gt_ggc_mx_lang_tree_node(void*)
>         ???:0
> 0x8ccda1 gt_ggc_mx_lang_tree_node(void*)
>         ???:0


Yeah, clang especially isn't a very rare package. And you're getting
errors that range from frontend crashes to GC crashes. This is very
unlikely to be a compiler bug on a specific file with unusual code.

An issue with your RAM (or some other hardware issue? overheating?
overclocking? it's possible...) is a very likely diagnosis, unfortunately.

Good luck.


-- 
Eli Schwartz


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  parent reply	other threads:[~2024-09-04  4:26 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 23:28 [gentoo-user] Package compile failures with "internal compiler error: Segmentation fault" Dale
2024-09-04  0:12 ` [gentoo-user] " Grant Edwards
2024-09-04  0:39   ` Dale
2024-09-04  4:16     ` corbin bird
2024-09-06 20:15     ` Dale
2024-09-06 23:17       ` Michael
2024-09-07  3:02         ` Dale
2024-09-07 22:12     ` Wols Lists
2024-09-08  1:59       ` Dale
2024-09-08 13:32         ` Michael
2024-09-08  9:15       ` Michael
2024-09-08 20:19         ` Wol
2024-09-04  7:53   ` Raffaele Belardi
2024-09-04  4:26 ` Eli Schwartz [this message]
2024-09-04 10:48 ` Dale
2024-09-04 11:05   ` Frank Steinmetzger
2024-09-04 11:21     ` Dale
2024-09-04 15:57       ` Peter Humphrey
2024-09-04 19:09       ` Grant Edwards
2024-09-04 21:08         ` Frank Steinmetzger
2024-09-04 21:22           ` Grant Edwards
2024-09-04 21:53             ` Dale
2024-09-04 22:07               ` Grant Edwards
2024-09-04 22:14                 ` Dale
2024-09-04 22:38                 ` Michael
2024-09-05  0:11                   ` Dale
2024-09-05  8:05                     ` Michael
2024-09-05  8:36                       ` Dale
2024-09-05  8:42                         ` Michael
2024-09-05 10:53                           ` Dale
2024-09-05 11:08                             ` Michael
2024-09-05 11:30                               ` Dale
2024-09-05 18:55                                 ` Frank Steinmetzger
2024-09-05 22:06                                   ` Michael
2024-09-06  0:43                                     ` Dale
2024-09-06 12:21                                       ` Michael
2024-09-06 21:41                                         ` Frank Steinmetzger
2024-09-07  9:37                                           ` Michael
2024-09-07 16:28                                             ` Frank Steinmetzger
2024-09-07 17:08                                           ` Mark Knecht
2024-09-14 19:46                                           ` Dale
2024-09-15 22:29                                             ` Frank Steinmetzger
2024-09-16 10:24                                               ` Dale
2024-09-07 22:48                                     ` Wols Lists
2024-09-08  9:37                                       ` Michael
2024-09-05  9:08                   ` Frank Steinmetzger
2024-09-05  9:36                     ` Michael
2024-09-05 10:01                       ` Frank Steinmetzger
2024-09-05 10:59                         ` Dale
2024-09-04 14:21     ` Grant Edwards
2024-09-04 11:37   ` Dale
2024-09-04 14:23     ` Grant Edwards
2024-09-04 15:58       ` Peter Humphrey
2024-09-04 19:28         ` Dale
2024-09-25 20:41 ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3b1883a6-cdf2-439b-b713-391e53a11d76@gentoo.org \
    --to=eschwartz@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox