Skip to content

Instantly share code, notes, and snippets.

@jcf
Created August 19, 2010 13:29
Show Gist options
  • Save jcf/537882 to your computer and use it in GitHub Desktop.
Save jcf/537882 to your computer and use it in GitHub Desktop.
Output from spork crash
Using RSpec
Preloading Rails environment
Loading Spork.prefork block...
No server is running
Running specs locally:
dyld: lazy symbol binding failed: Symbol not found: _rb_method_node
Referenced from: /Users/jcf/.rvm/gems/ruby-1.9.2-p0/gems/ruby-debug-base19-0.11.23/lib/ruby_debug.bundle
Expected in: flat namespace
dyld: Symbol not found: _rb_method_node
Referenced from: /Users/jcf/.rvm/gems/ruby-1.9.2-p0/gems/ruby-debug-base19-0.11.23/lib/ruby_debug.bundle
Expected in: flat namespace
zsh: trace trap bundle exec spork
@rbxbx
Copy link

rbxbx commented Aug 19, 2010

+1, but it seems to just be a ruby-debug19 issue, ie:

$ irb
>> require 'ruby-debug'
=> true
>> debugger
dyld: lazy symbol binding failed: Symbol not found: _rb_method_node
  Referenced from: /Users/dev/.rvm/gems/ruby-1.9.2-p0@iflail/gems/ruby-debug-base19-0.11.23/lib/ruby_debug.bundle
  Expected in: flat namespace

dyld: Symbol not found: _rb_method_node
  Referenced from: /Users/dev/.rvm/gems/ruby-1.9.2-p0@iflail/gems/ruby-debug-base19-0.11.23/lib/ruby_debug.bundle
  Expected in: flat namespace

Trace/BPT trap

@jcf
Copy link
Author

jcf commented Aug 19, 2010

I agree completely. It is a ruby-debug issue as opposed to a spork one.

@abuiles
Copy link

abuiles commented Aug 22, 2010

Hi guys I'm having the same problem right now, did you manage to figure it out what is causing it ?


I manage to solve the issue, put this in your Gemfile

gem 'ruby-debug-base19', "0.11.24"
gem 'ruby-debug19', "0.11.6"

that would fix the problem

@jcf
Copy link
Author

jcf commented Aug 23, 2010

@abuiles that fixes the problem for me. Thanks for the heads up!

@abuiles
Copy link

abuiles commented Aug 23, 2010

@jfc no probs :)

@rbxbx
Copy link

rbxbx commented Aug 23, 2010

@abuiles thanks sir it's nice to have debugging back :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment