Debugging

Utilities for better "print debugging"

Great Ruby debugging companion: pretty print Ruby objects to visualize their structure. Supports custom object formatting via plugins

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.

Convert directories, rpms, python eggs, rubygems, and more to rpms, debs, solaris packages and more. Win at package management without wasting pointless hours debugging bad rpm specs!

A debugging tool for your Ruby on Rails applications.

Debugging functionality for Ruby. This is completely rewritten debug.rb which was contained by the ancient Ruby versions.

A generic command line interface for ruby-debug.

Provides the Binding#of_caller method. Using binding_of_caller we can grab bindings from higher up the call stack and evaluate code in that context. Allows access to bindings arbitrarily far up the call stack, not limited to just the immediate caller. Recommended for use only in debugging situations. Do not use this in production apps.

Track and debug errors in your Ruby applications with ease using Rollbar. With this gem, you can easily monitor and report on exceptions and other errors in your code, helping you identify and fix issues more quickly. Rollbar's intuitive interface and advanced error tracking features make it the perfect tool for ensuring the stability and reliability of your Ruby applications.

An interface which glues ruby-debug to IDEs like Eclipse (RDT), NetBeans and RubyMine.

A generic command line interface for ruby-debug.

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.

Great Ruby debugging companion: pretty print Ruby objects to visualize their structure. Supports custom object formatting via plugins

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.

Adds methods to DebugInspector to allow for inspection of backtrace frames. The debug_inspector C extension and API were designed and built by Koichi Sasada, this project is just a gemification of his work. This library makes use of the debug inspector API which was added to MRI 2.0.0. Only works on MRI 2 and 3. Requiring it on unsupported Rubies will result in a no-op. Recommended for use only in debugging situations. Do not use this in production apps.

MetaWhere offers the ability to call any Arel predicate methods (with a few convenient aliases) on your Model's attributes instead of the ones normally offered by ActiveRecord's hash parameters. It also adds convenient syntax for order clauses, smarter mapping of nested hash conditions, and a debug_sql method to see the real SQL your code is generating without running it against the database. If you like the new AR 3.0 query interface, you'll love it with MetaWhere.

Ruby Jard provides an unified experience debugging Ruby source code in different platforms and \ editors.

Ever wondered which translations are being looked up by Rails, a gem, or simply your app? Wonder no more!

Hunting down random test failures can be very very difficult, sometimes impossible, but minitest-bisect makes it easy. minitest-bisect helps you isolate and debug random test failures. If your tests only fail randomly, you can reproduce the error consistently by using `--seed <num>`, but what then? How do you figure out which combination of tests out of hundreds are responsible for the failure? You know which test is failing, but what others are causing it to fail or were helping it succeed in a different order? That's what minitest-bisect does best.

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.

Debugging toolbar for Rack applications implemented as middleware

Letters brings Ruby debugging into the 21st century. It leverages print, the debugger, control transfer, even computer beeps to let you see into your code's state.

Sinatra Logging is a pain. This gem helps with wiring Access logs, Error logs, and plain debugging logs (i.e. logger.info, logger.warn, ... etc).

This plugin helps you setup and debug `ssh-doctor` forwarding for Capistrano deployment. It peforms a number of checks on the local machine as well as on the servers. Report output with suggested next steps is provided in case there are any errors with the setup.

A Hoe plugin to help you debug your C extensions. This plugin provides `test:gdb` and `test:valgrind` tasks (plus a few variants). As of v1.5 it also can generate a valgrind suppression from a previous test suite's log file. See the `Hoe::Debugging` module for a few configuration options. This plugin expects you to have `gdb` and `valgrind` available in your `PATH`.

Ruby support for Source Maps allows you to interact with Source Maps in Ruby. This lets you do things like concatenate different javascript files and still debug them as though they were separate files. See the spec for more information: https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit

Don't re-write web scrapers every time. Upton gives you a scraper template that's easy to use for debugging and doesn't hammer servers by default.

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.

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 file names, line numbers, classes, and methods contained the puts statements, 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, class names, method names, and 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.)

Flex is the ultimate ruby client for elasticsearch. It is powerful, fast and efficient, easy to use and customize. It covers ALL the elasticsearch API, and transparently integrates it with your app and its components, like Rails, ActiveRecord, Mongoid, ActiveModel, will_paginate, kaminari, elasticsearch-mapper-attachments, ... It also implements and integrates very advanced features like chainable scopes, live-reindex, cross-model syncing, query fragment reuse, parent/child relationships, templating, self-documenting tools, detailed debugging, ...

:: wmainfo-rb :: Author: Darren Kirby mailto:bulliver@badcomputer.org License: Ruby = Quick API docs = == Initializing == require 'wmainfo' foo = WmaInfo.new("someSong.wma") ... or ... foo = WmaInfo.new("someVideo.wmv", :encoding=>"UTF-16LE") (default encoding is ASCII) ... or ... foo = WmaInfo.new("someVideo.wmv", :debug=>1) == Public attributes == @drm :: 'true' if DRM present else 'false' @tags :: dict of strings (id3 like data) @info :: dict of variable types (non-id3 like data) @ext_info :: dict of variable types (non-id3 like data) from ASF_Extended_Content_Description_Object @headerObject :: dict of arrays (name, GUID, size and offset of ASF objects) @stream :: dict of variable types (stream properties data) == Public methods == print_objects :: pretty-print header objects hasdrm? :: returns True if file has DRM hastag?('str') :: returns True if @tags['str'] exists print_tags :: pretty-print @tags dict hasinfo?('str') :: returns True if @info['str'] exists print_info :: pretty-print @info dict print_stream :: pretty-print @stream dict For more/different documentation see http://badcomputer.org/unix/code/wmainfo/ == Thanks/Contributors == Ilmari Heikkinen sent in a fix for uninitialized '@ext_info'. Guillaume Pierronnet sent in a patch which improves character encoding handling.

motion_print is a RubyMotion friendly console logger and debugging tool.

Adds SQL analysis and debugging info to Rails applications.

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.

Simple wrapper over Android Debug Bridge command-line tool

Rack::Debug is a middleware that provides a simple interface to ruby-debug. Helps debug apps running in Passenger.

Provides rake tasks to ease the development and debugging of Grape APIs.

Adds middleware for debugging purposes

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

Debugging toolbar for Rack applications implemented as middleware. Based on logical-insight and rack-bug.

Enhanced show-doc (a.k.a ? command) for: $! $" $$ $& $' $* $+ $, $-0 $-F $-I $-K $-W $-a $-d $-i $-l $-p $-v $-w $. $0 $1 $2 $3 $4 $5 $6 $7 $8 $9 $: $; $< $= $> $? $@ $DEBUG $FILENAME $KCODE $LOADED_FEATURES $LOAD_PATH $PROGRAM_NAME $SAFE $VERBOSE $\ $_ $` $stderr $stdin $stdout $~ $⁄ BEGIN END __ENCODING__ __FILE__ __LINE__ alias and begin break case class def defined? do else elsif end ensure false for if in module next nil not or redo rescue retry return self super then true undef unless until when while yield

Adds an initializer that loads and starts the debugger, and a 'rake debug' task that tells Phusion Passenger to restart with debugging enabled. This makes it possible to do interactive debugging when using the Phusion Passenger Apache module - it does not require the standalone server.

The Sensu Core built-in debug handler

BackStage allows you to look behind the TorqueBox curtain, and view information about all of the components you have running. It includes support for remote code execution and log tailing to aid in debugging.

A small test framework that supports debugging test failures and errors when they happen.

== 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 &lt;tt&gt;Motion::Project::App.setup&lt;/tt&gt; 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 &lt;tt&gt;rake debug=1&lt;/tt&gt;, and off you go!

Simple way to print debug messages from ruby code directly to browser console

Launches Google Chrome instances and controls them via the Remote Debugging server

Ember (EMBEdded Ruby) is an [eRuby] template processor that allows debugging, reduces markup, and improves composability of eRuby templates.

Provides an Origen API to perform register read and write operations via the ARM_DEBUG protocol.