v>0.1.9 causes pry-stack_explorer to step through pry-debugger frames

[rking]

cat > Gemfile <<EOT
source :rubygems
gem 'pry'
gem 'pry-exception_explorer'
gem 'pry-debugger'
gem 'pry-stack_explorer'
gem 'micro_test'
EOT
bundle
bundle exec mt --demo --pry

Then you'll notice whereami is in the assert itself, which I think is on mciro_test to fix, but when you hit up you'll end up in:

From: /Users/rking/.rbenv/versions/1.9.3-p125/lib/ruby/gems/1.9.1/gems/pry-debugger-0.2.1/lib/pry-debugger/processor.rb @ line 18 PryDebugger::Processor#run:

Then the next one is: the command = catch(:breakout_nav) just a line above that, then the next is:

/Users/rking/.rbenv/versions/1.9.3-p125/lib/ruby/gems/1.9.1/gems/pry-debugger-0.2.1/lib/pry-debugger/pry_ext.rb @ line 14 Pry.start_with_pry_debugger:

Then it keeps messing up til several frames later. Here's the showterm of it:

http://showterm.io/1ed7b6e9426bbbfa85345

[rking]

Now then, if you downgrade PEE and PSE in the above to:

gem 'pry-exception_explorer', '0.1.9'
gem 'pry-debugger', '0.2.0'

(And otherwise the same Gemfile), the bundle exec mt --demo --pry works perfectly.

I can tell you that only downgrading pry-debugger to 0.2.0 does not fix it, but you cannot try without downgrading PEE because versions prior to 0.2.3 conflict with pry-debugger.

Thank you.

[rking]

This actually doesn't require mt. This minimal version fails in the same way:

echo 'def f; g end; def g; binding.pry end; f' > min.rb; bundle exec ruby -rpry min.rb