You are not logged in.

#1 2017-03-19 19:08:27

rvega
Member
From: Colombia
Registered: 2011-12-20
Posts: 25

Compiler segmentation faults. How to debug or properly report?

I use several packages from the AUR which require compiling, usually with gcc or gcc-multilib. Lately, I've been getting compilation failures when installing or updating some of these packages. The error message is always similar to:

internal compiler error: Segmentation fault
 /* Copyright (C) 1991-2017 Free Software Foundation, Inc.
 
Please submit a full bug report,
with preprocessed source if appropriate.
See <[url]https://bugs.archlinux.org/[/url]> for instructions.

And it happens while compilig different, seemingly random files. If I retry compiling, sometimes it works and sometimes it fails at a different file or line. I tried reinstalling gcc and base-devel but the error is still there. My system is up to date.

What information would be useful here and how do I get it, for submitting a formal bug report?

Last edited by rvega (2017-03-20 16:50:38)

Offline

#2 2017-03-19 19:39:08

loqs
Member
Registered: 2014-03-06
Posts: 1,684

Re: Compiler segmentation faults. How to debug or properly report?

The full output of makepkg from a run that shows this issue.
The matching output of ( see Core_dump#Examining_a_core_dump )

# coredumpctl info match

Please use code tags for command output ( https://bbs.archlinux.org/help.php#bbcode )

Offline

#3 2017-03-19 23:11:23

rvega
Member
From: Colombia
Registered: 2011-12-20
Posts: 25

Re: Compiler segmentation faults. How to debug or properly report?

Thanks @loqs,  here is the bug report I filed: https://bugs.archlinux.org/task/53377

Offline

#4 2017-03-19 23:53:21

Allan
Pacman Developer
From: Brisbane, AU
Registered: 2007-06-09
Posts: 10,534
Website

Re: Compiler segmentation faults. How to debug or properly report?

rvega wrote:

And it happens while compilig different, seemingly random files. If I retry compiling, sometimes it works and sometimes it fails at a different file or line. I tried reinstalling gcc and base-devel but the error is still there. My system is up to date.

Those are red flags for a hardware issue.

Offline

#5 2017-03-20 16:04:00

JohnBobSmith
Member
From: Canada
Registered: 2014-11-29
Posts: 645

Re: Compiler segmentation faults. How to debug or properly report?

Do you have the source code/packages in question handy? I could then test/build them myself and see if the ICE (Internal Compiler Error) persists on a known (mine) working system.

EDIT: Building ardour5 as linked in your bug report shortly. Will post results when possible. smile

Last edited by JohnBobSmith (2017-03-20 16:06:33)


I have been diagnosed with Bipolar Disorder. Therefore, I apologize in advance if the quality/content of my posts decline sharply, at any point.

Offline

#6 2017-03-20 18:02:16

JohnBobSmith
Member
From: Canada
Registered: 2014-11-29
Posts: 645

Re: Compiler segmentation faults. How to debug or properly report?

Alright, the package built fine on my system.

[jbs@dmb-gaming-laptop ~]$ gcc --version
gcc (GCC) 6.3.1 20170306
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[jbs@dmb-gaming-laptop ~]$ 

So allan is likely right that you're experiencing hardware issues. After all, its right above his name. wink But for completeness sake, its not gcc.


I have been diagnosed with Bipolar Disorder. Therefore, I apologize in advance if the quality/content of my posts decline sharply, at any point.

Offline

#7 2017-03-20 19:12:46

rvega
Member
From: Colombia
Registered: 2011-12-20
Posts: 25

Re: Compiler segmentation faults. How to debug or properly report?

Thanks for the replies, everyone. Now scanning for hard drive problems...

Offline

#8 2017-03-20 22:51:08

seth
Member
Registered: 2012-09-03
Posts: 1,825

Re: Compiler segmentation faults. How to debug or properly report?

https://www.archlinux.org/packages/extr … emtest86+/
Also see whether this is an OOM condition (do you have a swap file/partition? Do you compile in a tmpfs?)

Offline

#9 2017-03-21 21:09:46

rvega
Member
From: Colombia
Registered: 2011-12-20
Posts: 25

Re: Compiler segmentation faults. How to debug or properly report?

I ran a full hard drive sector test, memtest+ for a few hours (5 passes) and mprime to stress the cpu for a couple of hours. No errors found.
@seth, I do have a swap partition and I compile in the default location that makepkg uses (root partition).
Any other suggestion is appreciated.

Offline

#10 2017-03-21 21:44:12

seth
Member
Registered: 2012-09-03
Posts: 1,825

Re: Compiler segmentation faults. How to debug or properly report?

looking at the bug attachment, it segfaults from boost/lambda and boost/bind - as random as claimed: is "boost" a pattern?

Offline

#11 2017-03-21 21:46:22

andreyv
Member
From: Riga, Latvia
Registered: 2012-11-02
Posts: 31

Re: Compiler segmentation faults. How to debug or properly report?

Offline

#12 2017-04-09 16:45:37

rvega
Member
From: Colombia
Registered: 2011-12-20
Posts: 25

Re: Compiler segmentation faults. How to debug or properly report?

I could not diagnose any hardware issues but the problem remained. However, I'm not using that computer anymore and installed Manjaro in a new laptop where this issue is not present.
Thanks everyone for the help.

Offline

Board footer

Powered by FluxBB