Pry Byebug

Step-by-step debugging and stack navigation in Pry
Alternatives To Pry Byebug
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Navigation Stack2,249
13 years ago12October 22, 20186mitSwift
:octocat: NavigationStack is a stack-modeled UI navigation controller. Swift UI library made by @Ramotion -
12 days ago114C++
ROS Navigation stack. Code for finding where the robot is and how it can get somewhere else.
Pry Byebug1,92427,2903,2664 months ago29August 16, 202242mitRuby
Step-by-step debugging and stack navigation in Pry
Simple Stack1,309
a month ago8apache-2.0Java
[ACTIVE] Simple Stack, a backstack library / navigation framework for simpler navigation and state management (for fragments, views, or whatevers).
3 years ago17Kotlin
An Android library for managing multiple stacks of fragments
17 days ago18April 30, 202239mitKotlin
🛸 A pragmatic navigation library for Jetpack Compose
17 years ago2March 24, 20152otherObjective-C
A view controller that organizes multiple navigation controllers in a stack inspired by Evernote 5.0 app
Swiftui Navigation Stack739
6 months ago3January 04, 202117mitSwift
An alternative SwiftUI NavigationView implementing classic stack-based navigation giving also some more control on animations and programmatic navigation.
Vue Page Stack59911a day ago34September 11, 2020mitJavaScript
Routing and navigation for your Vue SPA. Vue3.0 单页应用导航管理器
3 months ago3August 29, 202211otherKotlin
Android fragment stack controller
Alternatives To Pry Byebug
Select To Compare

Alternative Project Comparisons


Version Build Inline docs

Adds step-by-step debugging and stack navigation capabilities to pry using byebug.

To use, invoke pry normally. No need to start your script or app differently. Execution will stop in the first statement after your binding.pry.

def some_method
  puts 'Hello World' # Run 'step' in the console to move here

some_method          # Execution will stop here.
puts 'Goodbye World' # Run 'next' in the console to move here.


MRI 2.4.0 or higher.



gem 'pry-byebug'

to your Gemfile and run

bundle install

Make sure you include the gem globally or inside the :test group if you plan to use it to debug your tests!


Step-by-step debugging

break: Manage breakpoints.

step: Step execution into the next line or method. Takes an optional numeric argument to step multiple times.

next: Step over to the next line within the same frame. Also takes an optional numeric argument to step multiple lines.

finish: Execute until current stack frame returns.

continue: Continue program execution and end the Pry session.

Callstack navigation

backtrace: Shows the current stack. You can use the numbers on the left side with the frame command to navigate the stack.

up: Moves the stack frame up. Takes an optional numeric argument to move multiple frames.

down: Moves the stack frame down. Takes an optional numeric argument to move multiple frames.

frame: Moves to a specific frame. Called without arguments will show the current frame.

Matching Byebug Behaviour

If you're coming from Byebug or from Pry-Byebug versions previous to 3.0, you may be lacking the 'n', 's', 'c' and 'f' aliases for the stepping commands. These aliases were removed by default because they usually conflict with scratch variable names. But it's very easy to reenable them if you still want them, just add the following shortcuts to your ~/.pryrc file:

if defined?(PryByebug)
  Pry.commands.alias_command 'c', 'continue'
  Pry.commands.alias_command 's', 'step'
  Pry.commands.alias_command 'n', 'next'
  Pry.commands.alias_command 'f', 'finish'

Also, you might find useful as well the repeat the last command by just hitting the Enter key (e.g., with step or next). To achieve that, add this to your ~/.pryrc file:

# Hit Enter to repeat last command
Pry::Commands.command /^$/, "repeat last command" do
  pry_instance.run_command Pry.history.to_a.last


You can set and adjust breakpoints directly from a Pry session using the break command:

break: Set a new breakpoint from a line number in the current file, a file and line number, or a method. Pass an optional expression to create a conditional breakpoint. Edit existing breakpoints via various flags.


break SomeClass#run            # Break at the start of `SomeClass#run`.
break Foo#bar if baz?          # Break at `Foo#bar` only if `baz?`.
break app/models/user.rb:15    # Break at line 15 in user.rb.
break 14                       # Break at line 14 in the current file.

break --condition 4 x > 2      # Change condition on breakpoint #4 to 'x > 2'.
break --condition 3            # Remove the condition on breakpoint #3.

break --delete 5               # Delete breakpoint #5.
break --disable-all            # Disable all breakpoints.

break                          # List all breakpoints.
break --show 2                 # Show details about breakpoint #2.

Type break --help from a Pry session to see all available options.


Note that all of the alternatives here are incompatible with pry-byebug. If your platform is supported by pry-byebug, you should remove any of the gems mentioned here if they are present in your Gemfile.

  • pry-debugger: Provides step-by-step debugging for MRI 1.9.3 or older rubies. If you're still using those and need a step-by-step debugger to help with the upgrade, pry-debugger can be handy.

  • pry-stack_explorer: Provides stack navigation capabilities for MRI 1.9.3 or older rubies. If you're still using those and need to navigate your stack to help with the upgrade, pry-stack_explorer can be handy.

  • pry-nav: Provides step-by-step debugging for JRuby.


See Getting Started with Development.


Subscribe to Tidelift to ensure pry-byebug stays actively maintained, and at the same time get licensing assurances and timely security notifications for your open source dependencies.

You can also help pry-byebug by leaving a small (or big) tip through Liberapay.

Security contact information

Please use the Tidelift security contact to report a security vulnerability. Tidelift will coordinate the fix and disclosure.


  • Gopal Patel (@nixme), creator of pry-debugger, and everybody who contributed to it. pry-byebug is a fork of pry-debugger so it wouldn't exist as it is without those contributions.
  • John Mair (@banister), creator of pry.

Patches and bug reports are welcome.

Popular Navigation Projects
Popular Stack Projects
Popular User Interface Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.