[M3commit] [modula3/cm3] 6e1d2c: Several fixes for Mac OS X 10.10.4 Yosemite. More ...

[Jay K]

I think I have it -- -g probably always crashed.I'm testing -g1 now. That seemed to work on a small test case.

We should perhaps fix -g though.It is a null dereference generating dwarf output.

A valid workflow in Xcode is to debug by name, you canenter the name of a process that isn't running yet, and then run cm3cg.

i.e. if you don't yet know how to use lldb on the command line andhaven't gone through the trouble of building/installing gdb.If gdb even still works.

 - Jay

Subject: Re: [M3commit] [modula3/cm3] 6e1d2c: Several fixes for Mac OS X 10.10.4 Yosemite. More ...
From: hosking at purdue.edu
Date: Thu, 6 Aug 2015 09:54:07 +1000
CC: m3commit at elegosoft.com
To: jay.krell at cornell.edu

This one rings a bell, but I can’t put my finger on it.Perhaps check the m3cc commit logs?
On Aug 6, 2015, at 4:48 AM, jaykrell <jay.krell at cornell.edu> wrote:Even then, we get:../src/types/ASCII.m3: In function 'ASCII_M3':../src/types/ASCII.m3:26:0: internal compiler error: Segmentation fault: 11Please submit a full bug report,with preprocessed source if appropriate.See <http://gcc.gnu.org/bugs.html> for instructions. m3_backend => 4m3cc (aka cm3cg) failed compiling: ASCII.mc
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3commit/attachments/20150806/7381f264/attachment-0002.html>