Bug 217376 - make buildworld exits with segfault
Summary: make buildworld exits with segfault
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 11.0-STABLE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Dimitry Andric
URL:
Keywords: crash, needs-qa
Depends on:
Blocks:
 
Reported: 2017-02-26 18:21 UTC by jaglover
Modified: 2018-05-28 19:55 UTC (History)
1 user (show)

See Also:


Attachments
Preprocessed source (867.05 KB, text/plain)
2017-02-26 18:21 UTC, jaglover
no flags Details
Scripts (3.91 KB, text/plain)
2017-02-26 18:22 UTC, jaglover
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description jaglover 2017-02-26 18:21:53 UTC
Created attachment 180319 [details]
Preprocessed source

I have been trying to upgrade my 10.3 system since 11.0 became stable. It always segfaults at the same place. I've commented out all lines in my make.conf.
Comment 1 jaglover 2017-02-26 18:22:34 UTC
Created attachment 180320 [details]
Scripts
Comment 2 jaglover 2017-02-27 17:34:14 UTC
Hardware: Atom D2500, 4 GB of RAM.
Comment 3 Dimitry Andric freebsd_committer freebsd_triage 2017-04-23 18:35:22 UTC
I've tried reproducing your error with clang 5.0.0, 4.0.0, 3.9.0, 3.8.0 and 3.7.1, but for me your sample compiles just fine.  All these compiles don't take a lot of memory either, so I think we can rule out crashes due to limited RAM.

Maybe the /usr/obj/usr/src/tmp/usr/bin/cc executable was built with CPU options which aren't valid for your hardware?  Are you able to get a backtrace and/or some more detailed debugging information?
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:44:20 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Comment 5 jaglover 2018-05-28 19:54:21 UTC
Can be closed as far I'm concerned. Thank you.