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.

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.

ruby-debug 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.

google-cloud-debugger is the official library for Stackdriver Debugger.

A interactive command line tool for evaluating and debugging the puppet language

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.

Developer tools for Trailblazer: debugger, activity visualizer and tracing.

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

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

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.)

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.

ruby-debug 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.

XML interface for 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.

openMSX-Builder is used for building the latest SVN checkouts of openMSX and openMSX-Debugger from their sourceforge repository. It also supports publishing the created builds to an external location via scp, announcing successfully published builds via Twitter and reporting build-errors via e-mail.

This is the simple REST client for Cloud Debugger API (Deprecated) V2. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the Cloud Debugger API (Deprecated), but note that some services may provide a separate modern client that is easier to use.

== DBT (Dependencies and deBugging Tool) DBT is a tool that helps declare dependencies (+app.files_dependencies+) and assists with debugging in a RubyMotion project. It looks for 'break', 'requires', and 'provides' commands (it does a *teensy* bit of code analyzing to provide some defaults) to make your RubyMotion +Rakefile+ and +debugger_cmds+ files short and consistent. To use, include this gem, and add +DBT.analyze(app)+ to your +Rakefile+ in the <tt>Motion::Project::App.setup</tt> block. In your source code you can add DBT commands and those will be translated into directives for +app.files_dependencies+ and +debugger_cmds+. Run +rake+ or <tt>rake debug=1</tt>, and off you go!

Lightweight Ruby debugger written in plain Ruby using the TracePoint API

== 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

The Cloud Debugger API allows applications to interact with the Google Cloud Debugger backends. It provides two interfaces: the Debugger interface and the Controller interface. The Controller interface allows you to implement an agent that sends state data -- for example, the value of program variables and the call stack -- to Cloud Debugger when the application is running. The Debugger interface allows you to implement a Cloud Debugger client that allows users to set and delete the breakpoints at which the state data is collected, as well as read the data that is captured. Note that google-cloud-debugger-v2 is a version-specific client library. For most uses, we recommend installing the main client library google-cloud-debugger instead. See the readme for more details.