debugger can't be installed on ruby 2.X

eddiefisher commented 10 years ago

ruby -v
ruby 2.1.2p80 (2014-03-01 revision 45231) [x86_64-darwin13.0]

gem install debugger -v '1.6.6'
Building native extensions.  This could take a while...
ERROR:  Error installing debugger:
    ERROR: Failed to build gem native extension.

    /Users/eddiefisher/.rvm/rubies/ruby-2.1-head/bin/ruby extconf.rb
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
    --with-opt-dir
    --with-opt-include
    --without-opt-include=${opt-dir}/include
    --with-opt-lib
    --without-opt-lib=${opt-dir}/lib
    --with-make-prog
    --without-make-prog
    --srcdir=.
    --curdir
    --ruby=/Users/eddiefisher/.rvm/rubies/ruby-2.1-head/bin/ruby
/Users/eddiefisher/.rvm/rubies/ruby-2.1-head/lib/ruby/2.1.0/fileutils.rb:1573:in `stat': No such file or directory @ rb_file_s_stat - ./212/ruby_debug.h (Errno::ENOENT)
    from /Users/eddiefisher/.rvm/rubies/ruby-2.1-head/lib/ruby/2.1.0/fileutils.rb:1573:in `block in fu_each_src_dest'
    from /Users/eddiefisher/.rvm/rubies/ruby-2.1-head/lib/ruby/2.1.0/fileutils.rb:1587:in `fu_each_src_dest0'
    from /Users/eddiefisher/.rvm/rubies/ruby-2.1-head/lib/ruby/2.1.0/fileutils.rb:1571:in `fu_each_src_dest'
    from /Users/eddiefisher/.rvm/rubies/ruby-2.1-head/lib/ruby/2.1.0/fileutils.rb:399:in `cp'
    from extconf.rb:83:in `block in <main>'
    from extconf.rb:82:in `each'
    from extconf.rb:82:in `<main>'

extconf failed, exit code 1

Gem files will remain installed in /Users/eddiefisher/.rvm/gems/ruby-2.1-head/gems/debugger-1.6.6 for inspection.
Results logged to /Users/eddiefisher/.rvm/gems/ruby-2.1-head/extensions/x86_64-darwin-13/2.1.0/debugger-1.6.6/gem_make.out

cldwalker commented 10 years ago

Thanks for reporting your issue! This is one of my 16 active issues. Use that link to check how soon your issue will be answered. Don't forget to check your issue against this project's CONTRIBUTING.md. Cheers.

SpringMT commented 10 years ago

Is this issue ongoing? I'm just in trouble with the issue.

colszowka commented 10 years ago

Yes, I am having this issue with 1.6.6 and against 2.1.2 as well.

tgautier commented 10 years ago

Same here. Issue with 1.6.6 with ruby 2.1.2 on OSX 10.9.2

caarlos0 commented 10 years ago

same here!

sjfbo commented 10 years ago

:+1: and there is a PR for that issue.

PikachuEXE commented 10 years ago

Same here....

lucascaton commented 10 years ago

+1

nathany commented 10 years ago

Support for Ruby 2.1.2p95 would be groovy.

granolocks commented 10 years ago

:+1:

mnsami commented 10 years ago

+1

organillero commented 10 years ago

Same here!

bmfreitas commented 10 years ago

+1

lmcdougall commented 10 years ago

+1

HokieTT commented 10 years ago

+1

colszowka commented 10 years ago

Hey folks, please refrain from posting spammy +1s and pinging everyone subscribed to this thread. I think the point that this is broken on Ruby 2.1.2 has been made and proved, and either someone with the time and knowledge will submit a fix PR or you tackle this and do the same. I don't think putting +1 comments on this thread will speed things up. Thanks!

tgautier commented 10 years ago

There's already a PR #126

lucascaton commented 10 years ago

@cldwalker @astashov @mark-moseley @nobu, Hey guys, any news from this one? Thanks.

jpstokes commented 10 years ago

I've having the same issue.

gmmeyer commented 10 years ago

I am having this problem on linux as well, it's not confined to mac.

cldwalker commented 10 years ago

For ruby 2.X debugging, I now recommend byebug or debugger2. I've updated the README to indicate this. Reasons for this:

debugger has never had full ruby 2.x support. An open call was made to the community more than a year ago but no one stepped up. See #47.
The rails community has thrown its weight behind byebug for 2.x debugging.

In a week, I will be closing all ruby2 issues including this one. I will hold off on closing them if someone takes up working on 2.X support. I'm happy to provide github and gem push access as needed. Is @astashov, @nobu, @sunaku, @windwiny or anyone else interested in adding 2.X support for debugger?

This requires doing the following with ko1's pull request, #69:

[ ] Resolve merge conflicts. A fair amount has landed on master since the pull request
[ ] Disable tests and features that have not been ported to 2.x e.g. post-mortem and threading. Disabling should only be done for 2.x rubies.
[ ] Ensure all tests pass on 2.X rubies
[ ] No longer depend on ruby internals (see #47 for some discussion). This means there should be no dependence on https://github.com/cldwalker/debugger-ruby_core_source. This should be resolved by the pull request but is important to state nontheless.

cldwalker commented 10 years ago

I am also looking for 1.9.X maintainers if anyone is interested

jasonzhao6 commented 10 years ago

What are the pros and cons of byebug vs debugger2?

nathany commented 10 years ago

Our reason for using debugger (with Ruby 2.1) is that pry-debugger currently depends on it. /cc @nixme

vasanthela commented 10 years ago

@nathany You can use pry-byebug instead of pry-debugger, and that avoids the dependency on debugger. It only supports MRI 2.0.0 or newer.

From its gemspec:

  # Dependencies
  gem.required_ruby_version = '>= 2.0.0'

  gem.add_runtime_dependency 'pry', '~> 0.9.12'
  gem.add_runtime_dependency 'byebug', '~> 2.7'