Seg fault while processing model #121

Closed
sixten opened this Issue Aug 4, 2012 · 13 comments

Comments

Projects
None yet
5 participants
Contributor

sixten commented Aug 4, 2012

I'm starting up a new Core Data project, and I realized that I didn't have the mogenerator installed on this Mac. So I:

  1. Installed mogenerator 1.2.6 with homebrew (which builds it from source tarball)
  2. Created my very basic model
  3. Tried to compile the model, with this result:
20993 Segmentation fault: 11  mogenerator --template-var arc=true
--model Wensleydale.xcdatamodeld/Wensleydale.xcdatamodel
--output-dir . --machine-dir _generated

I'm running Xcode 4.4 on Lion (10.7.4). I'm guessing this may, one way or another, be an issue with the newer tools. That's really the only unknown. (I've been a happy user of this tool for a while now, with no issues.)

On the off chance it was a format issue, I tried backing my model file back to the Xcode 3.2 format. No dice.

I also ran it on the models from a couple of older projects where I know I've been using mogenerator, and it also segfaults. I've been building that model with 1.26 on a different Mac successfully. That mogenerator was installed from homebrew a while back.

How can I gather more information for you to help diagnose this?

ryanjm commented Aug 12, 2012

I also just ran into a segmentation fault.

$: mogenerator --model ~/code/myApp/MyApp.xcdatamodeld/MyApp8.xcdatamodel --output-dir ~/code/myApp/Classes
[1]    53139 segmentation fault  mogenerator --model  --output-dir ~/code/myApp/Classes

Any help would be appreciated.

Owner

rentzsch commented Aug 13, 2012

What version of Xcode and OS X?

If either of you could provide a download link to a troublesome data model, that would make it possible to repro.

ryanjm commented Aug 13, 2012

Xcode: Version 4.4.1 (4F1003)
OSX: 10.7.4

I just did an install from homebrew like @sixten did.

I'll see if I can create a quick repo to replicate the issue in a little bit.

Contributor

sixten commented Aug 13, 2012

I should be able to post some models for you tomorrow. FWIW, the 1.2.6 binary compiled with the older tools, downloaded to the Mac I mentioned above, does not segfault on those same models. So it does appear to be dependent on the tools that compiled it.

On Aug 12, 2012, at 6:04 PM, Jonathan 'Wolf' Rentzsch notifications@github.com wrote:

What version of Xcode and OS X?

If either of you could provide a download link to a troublesome data model, that would make it possible to repro.


Reply to this email directly or view it on GitHub.

Owner

rentzsch commented Aug 13, 2012

Thanks guys.

Contributor

sixten commented Aug 13, 2012

I've zipped up a couple of the models that failed for me here: [link removed]

Let me know whether that works for you (I'll probably also take that file down once you have it).

Owner

rentzsch commented Aug 14, 2012

ok I can't examine it right now but I downloaded the .zip locally if you want to delete it

Owner

rentzsch commented Aug 14, 2012

@sixten what version of OS X and Xcode are you using? Wasn't able to repro here on 10.8.0/4.5-DP4 using 1.26 from homebrew or from github HEAD.

Contributor

sixten commented Aug 14, 2012

Xcode 4.4, OS X 10.7.4

ryanjm commented Aug 15, 2012

@rentzsch Is there anything I can help with? I figured you didn't need two sets of files.

hey guys.
open the mogenerator project in Xcode and set the min. deployment target to 10.7 (or whatever)
The latest Xcode seems to include the 10.8 SDK and targets 10.8 per default, even when building on 10.7 :-/
This fixed the issue for me

jlnr commented Aug 28, 2012

Thanks @floorjiann - that's indeed it.

@rentzsch rentzsch closed this in e426bec Aug 28, 2012

Owner

rentzsch commented Aug 28, 2012

@floorjiann @jlnr thanks guys for tracking this one down and verifying the fix!

ddrccw pushed a commit to ddrccw/mogenerator that referenced this issue Jan 20, 2014

Fix seg fault on 10.7 by explicitly setting
deployment target to 10.6. Closes #121.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment