Segmentation fault on OS X 10.9.3 with fresh Haxe/OpenFl/Lime/Flixel

187 views
Skip to first unread message

Shaun Inman

unread,
May 28, 2014, 7:24:05 PM5/28/14
to
HaxeFlixel looks super promising. I just got everything installed and I am able to compile and run the Flash version of HelloWorld but `lime test mac` produces the following output:

Called from ? line 1
Called from CommandLineTools.hx line 998
Called from CommandLineTools.hx line 23
Called from a C function
Called from CommandLineTools.hx line 108
Called from CommandLineTools.hx line 205
Called from platforms/MacPlatform.hx line 217
Called from helpers/IconHelper.hx line 62
Called from helpers/IconHelper.hx line 361
Called from helpers/ImageHelper.hx line 25
Called from openfl/display/BitmapData.hx line 15
Called from a C function
Called from openfl/display/BitmapData.hx line 62
Uncaught exception - Segmentation fault

Here it is again with the -verbose flag:

 |. _ _  _
 ||| | ||_|
 ||| | ||_.

Lime Command-Line Tools (1.5.3)

Initializing project...
Using project file: ~/Documents/Haxe/HelloWorld/project.xml
Reading HXCPP config: ~/.hxcpp_config.xml
Using target platform: MAC

Running command: UPDATE
 - Copying template file: /usr/lib/haxe/lib/lime-tools/1,5,3/templates/haxe/DefaultAssetLibrary.hx -> export/mac64/cpp/haxe/DefaultAssetLibrary.hx
 - Copying template file: /usr/lib/haxe/lib/openfl/2,0,0-beta,2/templates/haxe/DefaultAssetLibrary.hx -> export/mac64/cpp/haxe/DefaultAssetLibrary.hx
 - Copying template file: /usr/lib/haxe/lib/openfl/2,0,0-beta,2/templates/haxe/NMEPreloader.hx -> export/mac64/cpp/haxe/NMEPreloader.hx
 - Copying template file: /usr/lib/haxe/lib/lime/0,9,9/templates/haxe/ApplicationMain.hx -> export/mac64/cpp/haxe/ApplicationMain.hx
 - Copying template file: /usr/lib/haxe/lib/lime/0,9,9/templates/haxe/lime/AssetData.hx -> export/mac64/cpp/haxe/lime/AssetData.hx
 - Copying template file: /usr/lib/haxe/lib/openfl/2,0,0-beta,2/backends/native/templates/haxe/ApplicationMain.hx -> export/mac64/cpp/haxe/ApplicationMain.hx
 - Copying template file: /usr/lib/haxe/lib/openfl/2,0,0-beta,2/backends/native/templates/haxe/NMEPreloader.hx -> export/mac64/cpp/haxe/NMEPreloader.hx
 - Copying template file: /usr/lib/haxe/lib/lime/0,9,9/templates/cpp/hxml/debug.hxml -> export/mac64/cpp/haxe/debug.hxml
 - Copying template file: /usr/lib/haxe/lib/lime/0,9,9/templates/cpp/hxml/final.hxml -> export/mac64/cpp/haxe/final.hxml
 - Copying template file: /usr/lib/haxe/lib/lime/0,9,9/templates/cpp/hxml/release.hxml -> export/mac64/cpp/haxe/release.hxml
 - Copying template file: /usr/lib/haxe/lib/lime/0,9,9/templates/mac/Info.plist -> export/mac64/cpp/bin/HelloWorld.app/Contents/Info.plist
 - Copying template file: /usr/lib/haxe/lib/lime/0,9,9/templates/mac/Entitlements.plist -> export/mac64/cpp/bin/HelloWorld.app/Contents/Entitlements.plist
Called from ? line 1
Called from CommandLineTools.hx line 998
Called from CommandLineTools.hx line 23
Called from a C function
Called from CommandLineTools.hx line 108
Called from CommandLineTools.hx line 205
Called from platforms/MacPlatform.hx line 217
Called from helpers/IconHelper.hx line 62
Called from helpers/IconHelper.hx line 361
Called from helpers/ImageHelper.hx line 25
Called from openfl/display/BitmapData.hx line 15
Called from a C function
Called from openfl/display/BitmapData.hx line 62
Uncaught exception - Segmentation fault

 `lime test neko` and `lime test ios` produce the same.

I'm on the latest version of OS X—and Xcode and its command line tools if it matters. I am at a complete loss as to how to proceed. Here's the output from `haxelib list`:

actuate: [1.7.3]
flixel-addons: [1.1.0]
flixel-demos: [1.1.1]
flixel-templates: [1.0.2]
flixel-tools: [1.0.2]
flixel-ui: [1.0.2]
flixel: [3.3.4]
hxcpp: [3.1.37]
lime-tools: [1.5.3]
lime: [0.9.9]
openfl-samples: [1.3.0]
openfl: [2.0.0-beta.2]
swf: [1.5.2]

What am I missing? Thanks for any insight into the problem!

Shaun Inman

unread,
May 28, 2014, 8:14:24 PM5/28/14
to haxef...@googlegroups.com
Things I've tried in the meantime (with the help of Aaron McLeod on Twitter): 

Downgrading openfl to 1.4.0. 
Installing openfl-native
Installing hxlibc

And reinstalling everything from scratch. My list after all that:

actuate: [1.7.3]
flixel-addons: [1.1.0]
flixel-demos: [1.1.1]
flixel-templates: [1.0.2]
flixel-tools: [1.0.2]
flixel-ui: [1.0.2]
flixel: [3.3.4]
hxcpp: [3.1.37]
hxlibc: [1.1.4]
lime-tools: [1.5.3]
lime: [0.9.9]
openfl-html5: [1.4.2-beta]
openfl-native: [1.4.0]
openfl-samples: [1.3.0]
openfl: 1.3.0 1.4.0 [2.0.0-beta.2]
swf: [1.5.2]

Same errors though. (The Flash build stopped compiling after downgrading openfl to 1.4.0 so I set it back to 2.0.0-beta.2.)

Rafael Oliveira

unread,
May 28, 2014, 10:44:49 PM5/28/14
to
Something that helped me to see what is wrong, is to compile to html5, and then look for errors in web inspector.

Shaun Inman

unread,
May 29, 2014, 8:51:50 AM5/29/14
to
Thanks for the assistance, Rafael. Unfortunately `lime test html5` produces the following error:

export/html5/haxe/NMEPreloader.hx:5: lines 5-115 : Class not found : Sprite

(This is with an empty project created with `flixel tpl -n "Test"`.)

Gama11

unread,
May 29, 2014, 9:17:11 AM5/29/14
to haxef...@googlegroups.com
That error is related to openfl-bitfive, the default HTML5 backend of flixel. It's not compatible with OpenFL 2.0.0 yet.

You can use OpenFL's backend by adding this to your xml before including flixel:
<set name="no-custom-backend" />

Not really sure what could be causing that segfault, but it definitely seems like an OpenFL / Lime issue, not a flixel one. There's a related thread here in the OpenFL forums.

Shaun Inman

unread,
May 29, 2014, 9:41:04 AM5/29/14
to haxef...@googlegroups.com
Yeah, I'm not really worried about building for HTML5 yet. I'm primarily interested in native builds. I'll keep an eye on that OpenFL thread (it was created 10 minutes before you posted about it, so it didn't exist when I posted my original question). Thanks for the point in the right direction though!

Gama11

unread,
May 29, 2014, 2:33:37 PM5/29/14
to haxef...@googlegroups.com
There've just been new releases of lime / OpenFL that should fix this issue. :)
Reply all
Reply to author
Forward
0 new messages