Re: llvm issue

2018-02-24 Thread Jordon
I think you're on to something.  I just noticed that there is a clang++.core file that is 1,621,798,448 bytes. I have never looked at the login.conf file (or really, that whole part of bsd) before.  What exactly am I going to change?  Under the 'default:' section, I changed both datasize

Re: llvm issue

2018-02-24 Thread Jordon
On 02/24/2018 04:00 AM, Stuart Henderson wrote: No crash here, but it does use 1.6GB during compile. Try raising memory limits in login.conf (you'll need a new login session, which might mean restarting X). Or try restricting with ulimit to see if you can trigger the crash on other OS. The

Re: llvm issue

2018-02-24 Thread Stuart Henderson
On 2018/02/23 17:21, Jordon wrote: > I am running the latest snapshot (Feb 21) and discovered that some changes I > made to my hobby project this evening make clang++ crash.  It builds find on > linux with clang 3.8 and a High Sierra machine running whatever version > Apple ships with that. No

Re: llvm issue

2018-02-23 Thread Jordon
On 02/23/2018 05:21 PM, Jordon wrote: I am running the latest snapshot (Feb 21) and discovered that some changes I made to my hobby project this evening make clang++ crash.  It builds find on linux with clang 3.8 and a High Sierra machine running whatever version Apple ships with that. The

llvm issue

2018-02-23 Thread Jordon
I am running the latest snapshot (Feb 21) and discovered that some changes I made to my hobby project this evening make clang++ crash.  It builds find on linux with clang 3.8 and a High Sierra machine running whatever version Apple ships with that. The output message is this: clang++  -Wall