Skip to content
This repository

Binding navigation commands for Pry to make a simple debugger

tag: v0.0.4

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 lib
Octocat-spinner-32 .gitignore Initial attempt at basic 'step' and 'next' commands November 29, 2011
Octocat-spinner-32 CHANGELOG.md
Octocat-spinner-32 Gemfile Initial attempt at basic 'step' and 'next' commands November 29, 2011
Octocat-spinner-32 LICENSE License December 03, 2011
Octocat-spinner-32 README.md
Octocat-spinner-32 Rakefile Initial attempt at basic 'step' and 'next' commands November 29, 2011
Octocat-spinner-32 pry-nav.gemspec
README.md

pry-nav

Simple execution control in Pry

Teaches Pry about step, next, and continue to create a simple debugger.

To use, invoke pry normally:

def some_method
  binding.pry          # Execution will stop here.
  puts 'Hello World'   # Run 'step' or 'next' in the console to move here.
end

pry-nav is not yet thread-safe, so only use in single-threaded environments.

Rudimentary support for pry-remote is also included. Ensure pry-remote is loaded or required before pry-nav. For example, in a Gemfile:

gem 'pry'
gem 'pry-remote'
gem 'pry-nav'

Debugging functionality is implemented through set_trace_func, which imposes a large performance penalty. pry-nav traces only when necessary, but due to a workaround for a bug in 1.9.2, the console will feel sluggish. Use 1.9.3 for best results and almost no performance penalty.

Contributing

Patches and bug reports are welcome. Just send a pull request or file an issue. Project changelog.

Acknowledgments

Something went wrong with that request. Please try again.