16

I'm using ruby 2.0.0-p195 on OSX. pry-debugger does not work (step/continue/next all appear to work like continue). Is there a pry debugging gem that works with ruby 2.0?

update: pry-debugger and pry-byebug both appear to work with with ruby 2.0.0-p195 in a simple project. I have some other conflict that is causing both to fail when using binding.pry in tests...

update: pry-byebug is working for me with the latest ruby 2.0 release, 2.0.0-p247, with pry-byebug 1.1.1 & byebug 1.5.0

tee
  • 4,149
  • 1
  • 32
  • 44
  • So pry-byebug is not working in your tests? I am the mantainer, feel free to open an issue if necessary. – deivid May 27 '13 at 21:13
  • Thanks @deivid. I will open an issue if I can reproduce it in a simple project - I haven't been able to isolate what's causing the problem yet. I copied my Gemfile into a separate blank rails project & debugging works there in both pry-debugger and pry-byebug, so I'm currently at a loss. – tee May 28 '13 at 15:39
  • 1
    Hope you get it sorted out, if I can help let me know! – deivid May 28 '13 at 20:33
  • Also looking for a solution to this issue, tee – JoshJordan Jul 04 '13 at 16:54
  • +1 on the ruby 2.0 and pry-debugger interpreting every command as `continue` – user527662 Feb 17 '14 at 01:28

2 Answers2

23

pry-byebug 1.1.1+ works with ruby 2.0.0-p247. It's a fork of pry-debugger & works with ruby 2.0+ only.

gem 'pry-byebug'

https://github.com/deivid-rodriguez/pry-byebug

updated with version numbers

tee
  • 4,149
  • 1
  • 32
  • 44
0

i found that removing pry-nav from my gemfile returned functionality to next. see also: issue #9

Alex Moore-Niemi
  • 2,913
  • 2
  • 24
  • 22