Brett on 09 Jul, 2012 12:36 AM
If there's no external custom processor set up, then something may be wrong with the binary for Marked itself. I'm going to recommend deleting Marked using Launchpad (hold down Option and click the X). Go back to the App Store and go to Purchases and install again. Let me know if the problem persists.
Brett on 09 Jul, 2012 01:57 AM
Unfortunately none of this has given me any clues so far. Has anything on your system changed recently? Upgrades, system utilities, etc.? I know you would have mentioned it already if there was anything major, but can you think of anything else that might have happened around the time Marked stopped working?
Sorry for such an unscientific question, these crash reports and debugging measures just aren't making sense yet.
Brett on 09 Jul, 2012 02:15 AM
That could possibly be the issue. Around the point that it's crashing, Marked is calling out to Ruby to do some string handling. It looks for the default OS X ruby processor, and if that failed it would error out in a similar fashion (I need better error handling for that scenario, but I haven't run into it being an issue before). Did your upgrade modify the default Ruby, or are you using something like rvm or rbenv?
It's odd that the symlink for Ruby appears to be correct and still have issues... what do you get if you run:
If it's not there, then you have a larger
problem. You should be able to solve it by linking your rvm 1.9.3
binary there, but you may run into other problems later. Given that
the symlink is already broken, though, I don't think it can hurt to
try this. Remove /usr/bin/ruby as above, then run: