The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug
....
/Users/dnagir/.rvm/gems/ruby-1.9.2-p290/gems/rb-appscript-0.6.1/lib/_aem/connect.rb:86: [BUG] Segmentation fault
ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-darwin11.1.0]
Currently I get the segmentation fault error:
More stuff:
Why I need that to work - https://github.com/guard/guard-rspec/issues/60 Related issue - https://github.com/scottdavis/growl_notify/issues/6
Suggested workaround was to initialise growl_notify in each fork. Probably can be done manually, but would be nice if
guard-spork
could do it.Thanks a lot in advance.