Byebug is a Ruby debugger. It's implemented using the TracePoint C API for execution control and the Debug Inspector C API for call stack navigation. The core component provides support that front-ends can build on. It provides breakpoint handling and bindings for stack frames among other things and it comes with an easy to use command line interface.

debugger is a fast implementation of the standard Ruby debugger debug.rb. It is implemented by utilizing a new Ruby C API hook. The core component provides support that front-ends can build on. It provides breakpoint handling, bindings for stack frames among other things.

Combine 'pry' with 'debugger'. Adds 'step', 'next', and 'continue' commands to control execution.

Provide Ruby core source files for C extensions that need them.

Turn Pry into a primitive debugger. Adds 'step' and 'next' commands to control execution.

debase is a fast implementation of the standard Ruby debugger debug.rb for Ruby 2.0. It is implemented by utilizing a new Ruby TracePoint class. The core component provides support that front-ends can build on. It provides breakpoint handling, bindings for stack frames among other things.

gc debugger, logger and profiler for rgengc in ruby 2.1

Lightweight Ruby debugger written in plain Ruby using the TracePoint API

pry-doc + pry-docmore + pry-debugger + pry-stack_explorer + pry-rescue + bond + jist

Proof of concept debugger in plain Ruby

A debugger for Jekyll templates

Rubinius debugger.

Linecache is a module for reading and caching lines. This may be useful for example in a debugger where the same lines are shown many times.

Advanced debugger for ruby with natural `next` across blocks, debug of dynamic calls, stepping into function by name, etc..

== Description A gdb-like Ruby debugger with both high and low-level debugging support. To provide the advanced features this version works only with a patched MRI Ruby 2.1.5 runtime. For a version that works with Ruby 1.9.3, install a version starting with 1.93

Debuggers are great! They help us troubleshoot complicated programming problems by inspecting values produced by code, line by line. They are invaluable when trying to understand what is going on in a large application composed of thousands or millions of lines of code. In day-to-day test-driven development and simple debugging though, a puts statement can be a lot quicker in revealing what is going on than halting execution completely just to inspect a single value or a few. This is certainly true when writing the simplest possible code that could possibly work, and running a test every few seconds or minutes. Problem is you need to locate puts statements in large output logs, know which methods were invoked, find out what variable names are being printed, and see nicely formatted output. Enter puts_debuggerer. A guilt-free puts debugging Ruby gem FTW that prints file names, line numbers, code statements, and formats output nicely courtesy of awesome_print. Partially inspired by this blog post: https://tenderlovemaking.com/2016/02/05/i-am-a-puts-debuggerer.html (Credit to Tenderlove.)

debugger is a fast implementation of the standard Ruby debugger debug.rb. It is implemented by utilizing a new Ruby C API hook. The core component provides support that front-ends can build on. It provides breakpoint handling, bindings for stack frames among other things.

A pure-ruby debugger. No more puts "HERE!!!" or p :var => var, :other => other until you find what caused the bug. Just add a breakpoint and see the value of any variable.

Readapt is a Ruby debugger that natively supports the Debug Adapter Protocol. Features include next/step in/step out, local and global variable data, and individual thread control.

In showing a long lists, sometimes one would prefer to see the value arranged aligned in columns. Some examples include listing methods of an object or debugger commands. See Examples in the rdoc documentation for examples.