In the series ‘How it works’ I look at awesome code of others. This week I look at Byebug a Ruby 2.0 debugger gem.

What is Byebug?

Byebug is an amazing ruby 2.0 debugger gem. It allows for debugging of ruby 2.0 using the Tracepoint API. It is a gem with native extensions meaning it requires C compilation to be used. We are looking at byebug 1.8.2 in this post.

Why am I reviewing Byebug?

Byebug is the first 2.0 debugger. It’s elegant, easy to use. And written by an amazing developer David Rodriguez. It’s the default reference project for anyone who wants to write native, well tested-gem.


  • REPL - The debugger, the inspector, the thing where you type commands after it has hit a breakpoint. REPL stands for Read-eval-print-loop.


Byebug consists out of a couple of parts.

  • C extension with hooks to the Tracepoint API and deals with low level concepts such as stack frames.
  • A breakpoint and catchpoint system
  • A ruby support library with acts as a bridge to the C API and allows for command processing and a REPL.
  • A beautiful test suite

Personally, I find the code and the library absolutely stunning. It’s both beautiful and elegant.

The gem file structure

The command tree comes up with the following file structure. I’ve removed a lot of files. But this is the basic outline.

├── Rakefile
├── bin
│   └── byebug
├── byebug.gemspec
├── ext
│   └── byebug
│       ├── Makefile
│       ├── breakpoint.c
│       ├── breakpoint.o
│       ├── byebug.bundle
│       ├── byebug.c
│       ├── byebug.h
│       ├── byebug.o
│       ├── context.c
│       ├── context.o
│       ├── extconf.rb
├── lib
│   ├── byebug
│   │   ├── command.rb
│   │   ├── commands
│   │   │   ├── breakpoints.rb
│   │   │   ├── ....
│   │   ├── context.rb
│   │   ├── remote.rb
│   │   └── ....
│   ├── byebug.bundle
│   └── byebug.rb
├── logo.png
└── test
    ├── examples
    │   ├── breakpoint.rb
    │   └── variables.rb
    ├── stepping_test.rb
    ├── support
    │   ├── breakpoint.rb
    │   ├── context.rb
    │   ├── matchers.rb
    │   ├── test_dsl.rb
    │   └── test_interface.rb
    └── variables_test.rb
10 directories, 131 files

Let’s go over them quickly:

  • The Rakefile contains tasks to build and test the gem. Rake compile compiles the gem using the rake-compiler gem to compile native extensions. The output of the C extension goes to ./lib/byebug.bundle. After which require will load it. Check my other article on making a native gem for details on how this works.
  • The byebug.gemspec contains the dependencies used and the specification for byebug. You can see its a native gem because it has the s.extensions defined.
require File.dirname(__FILE__) + '/lib/byebug/version' do |s|        = 'byebug'
  s.version     = Byebug::VERSION
  s.authors     = ['David Rodriguez', 'Kent Sibilev', 'Mark Moseley']       = '[email protected]'
  s.license     = 'BSD'
  s.homepage    = ''
  s.summary     = %q{Ruby 2.0 fast debugger - base + cli}
  s.description = %q{Byebug is a Ruby 2.0 debugger. It's implemented using the
    Ruby 2.0 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.}

  s.required_ruby_version     = '>= 2.0.0'

  s.files            = `git ls-files`.split("\n")
  s.test_files       = `git ls-files -- test/*`.split("\n")
  s.executables      = ['byebug']
  s.extra_rdoc_files = ['']
  s.extensions       = ['ext/byebug/extconf.rb']

  s.add_dependency "columnize", "~> 0.3.6"
  s.add_dependency "debugger-linecache", '~> 1.2.0'

  s.add_development_dependency 'rake', '~> 10.1.0'
  s.add_development_dependency 'rake-compiler', '~> 0.9.1'
  s.add_development_dependency 'mocha', '~> 0.14.0'

You can see Byebug depends on rake, rake-compiler and mocha as development dependencies. And debugger-linecache (responsible for caching lines of code for showing context) and columnize (responsible for showing information in columns) as runtime dependencies.

Let’s continue:

  • The ./lib/byebug directory contains the debugging support framework written in Ruby. And handles command processing for the REPL and code for managing breakpoints.
  • The ./test directory contains the tests for testing the gem.

The debugging process explained

The debug process uses an internal ruby API called TracePoint, which basically allows you to hook into the Ruby interpreter and execution process.

You can register a callback (hook) whenever a certain ruby line gets executed or when a certain event happens such as an exception thrown or returned from a method. Byebugs works by hooking into these calls using the TracePoint API.

The basic process (highly oversimplified) works like this:

  • You run your regular ruby program.
  • You require the byebug gem.
  • Byebug registers a couple of Tracepoint events using the tracepoint API from C. (In pseudo code: ‘call-this-hook-on-every-executed-ruby-line’, and a ‘call-this-hook-when-an-exception-occurs’ event)
  • It starts the tracepoint API and Byebug’s hook code gets called on every line.
  • It checks whether there are breakpoints defined for that line and file, and if so it breaks into the debug REPL. And gives you a prompt, where it waits for commands.
  • Additionally when a exception happens it breaks into the REPL as well.

Something to understand is, is that the code that is executed when a tracepoint is hit, is not being trace-pointed. Which is good or else we would end up in some weird tracepoint’ception.

I’ve build a small pseudo debugger in Ruby to explain the concept. Save it as tinydebug.rb and run this via ruby tinydebug.rb

state = :break; size = 0

# Here we hook into the TracePoint API, this block gets executed on every line.
trace = do |tp|

  lines = /\n/
  line =  lines[tp.lineno-1]

  puts "#{tp.path}: #{tp.lineno} - #{line}"
  p tp.binding.eval('local_variables')

  if state == :step
    if size == caller.size then state = :break end

  if state == :break
    action = (gets).strip
    puts "use n,s,bt" unless %w(s bt n).include? action

    if action == 's'
      state = :step
      size = caller.size

# From here on we enable the tracepoint API

puts "Use n to execute next, and s to step over a method"

def myfunc
  a = "im a local val"
  puts "Hey i am in a method"
  puts "I'm in a method"

puts "line one"
puts "line two"

How the C extension works

A part of Byebug is written in C. This is primarily because of the following reasons:

  • Speed. It’s fast. Breakpoint checking and the tracepoint callbacks are done in C.
  • Low level access. Some things like binding-as-caller are not accessible from Ruby and therefore done in C.

A quick glance of some interesting lines and files in C.

In byebug.c the Init_byebug gets called when the C library gets loaded.

  mByebug = rb_define_module("Byebug");
  rb_define_module_function(mByebug, "setup_tracepoints",
                                     Byebug_setup_tracepoints, 0);
  rb_define_module_function(mByebug, "remove_tracepoints",
                                     Byebug_remove_tracepoints, 0);
  rb_define_module_function(mByebug, "context", Byebug_context, 0);
  rb_define_module_function(mByebug, "breakpoints", Byebug_breakpoints, 0);
  rb_define_module_function(mByebug, "add_catchpoint",
                                     Byebug_add_catchpoint, 1);
  rb_define_module_function(mByebug, "catchpoints", Byebug_catchpoints, 0);
  rb_define_module_function(mByebug, "_start", Byebug_start, 0);
  ... SNIP ..

You can see here it defined a module named Byebug.

If we take a look at Byebug_start you can see that it will setup the tracepoints in case it has not yet been registered.

static VALUE
Byebug_start(VALUE self)
  VALUE result;

    result = Qfalse;
    result = Qtrue;

  if (rb_block_given_p())
    rb_ensure(rb_yield, self, Byebug_stop, self);

  return result;

You can see here which tracepoints are registered, in short ‘exception raised’, ‘line execution’, ‘class’ and ‘return’ events.

static VALUE
Byebug_setup_tracepoints(VALUE self)
  if (catchpoints != Qnil) return Qnil;

  breakpoints = rb_ary_new();
  catchpoints = rb_hash_new();
  context = context_create();

  tpLine = rb_tracepoint_new(Qnil,
    process_line_event, NULL);

  tpCall = rb_tracepoint_new(Qnil,
    process_call_event, NULL);

  tpCCall = rb_tracepoint_new(Qnil,
    process_c_call_event, NULL);

  tpReturn = rb_tracepoint_new(Qnil,
    process_return_event, NULL);

  tpCReturn = rb_tracepoint_new(Qnil,
    process_c_return_event, NULL);

  tpRaise = rb_tracepoint_new(Qnil,
    process_raise_event, NULL);


  return Qnil;

The actual processing of the lines happens in the method process_line_event.

static void
process_line_event(VALUE trace_point, void *data)
  VALUE breakpoint = Qnil;
  VALUE file    = rb_tracearg_path(trace_arg);
  VALUE line    = rb_tracearg_lineno(trace_arg);
  VALUE binding = rb_tracearg_binding(trace_arg);
  int moved = 0;


  if (dc->stack_size == 0) dc->stack_size++;

  if (dc->last_line != rb_tracearg_lineno(trace_arg) ||
      dc->last_file != rb_tracearg_path(trace_arg))
    moved = 1;

  if (RTEST(tracing))
    call_at_tracing(context, dc, file, line);

  if (moved || !CTX_FL_TEST(dc, CTX_FL_FORCE_MOVE))
    dc->steps = dc->steps <= 0 ? -1 : dc->steps - 1;
    if (dc->stack_size <= dc->dest_frame)
      dc->lines = dc->lines <= 0 ? -1 : dc->lines - 1;
      dc->dest_frame = dc->stack_size;

  if (dc->steps == 0 || dc->lines == 0 ||
       breakpoint = find_breakpoint_by_pos(breakpoints, file, line, binding)))))
    call_at_line_check(context, dc, breakpoint, file, line);


You can see here the call to find_breakpoint_by_pos which brings us to the following.

How breakpoints are implemented

Breakpoints are not a ruby concept, but one created by byebug. What happens under the hood is the following:

  • The Tracepoint hook gets called on every line being executed find_breakpoint_by_pos
  • Byebug checks this line against its collection of breakpoints. In this breakpoint collection there is a filename, and a line-number. It checks if the current file and line-number match. If so it returns a breakpoint.
  • The method call_at_line_check is called with given breakpoint.
  • That will call call_at_breakpoint
static VALUE
call_at_breakpoint(VALUE context_obj, debug_context_t *dc, VALUE breakpoint)
  dc->stop_reason = CTX_STOP_BREAKPOINT;
  return call_at(context_obj, dc, rb_intern("at_breakpoint"), 1, breakpoint, 0);
  • And that will call the method at_breakpoint on the context.rb object.
def at_breakpoint(brkpnt)
  handler.at_breakpoint(self, brkpnt)

And the handler will show the REPL.

How stepping works

Stepping is nothing more then breaking out of the REPL, and let ruby continue is next line. And then begin called back into the REPL.

How stepping over works

Stepping over is a bit more complicated. Stepping over works by checking the current length of the stack and saving this in a variable. Then continue away from the REPL and when called back to the Tracepoint check whether the current stack-frame size is the same as the one saved, if this is the case break into the REPL.

This way, when going into a new method the stack-frame size is higher than the one saved, so keep going executing every line without breaking until the stack size length is the same as the that is saved.

The REPL (command processor)

The command processor, is nothing more then an abstraction layer over the REPL. It basically allows for pluggable commands. You can find the code of this in lib/bybug/commands

module Byebug
  # Implements byebug "continue" command.
  class ContinueCommand < Command
    self.allow_in_post_mortem = true
    self.need_context         = false

    def regexp
      /^\s* c(?:ont(?:inue)?)? (?:\s+(\S+))? \s*$/x

    def execute
      if @match[1] && !@state.context.dead?
        filename = File.expand_path(@state.file)
        return unless line_number = get_int(@match[1], "Continue", 0, nil, 0)
        return errmsg "Line #{line_number} is not a stopping point in file " \
                      "\"#{filename}\"\n" unless

        Byebug.add_breakpoint filename, line_number

    class << self
      def names

      def description
        %{c[ont[inue]][ nnn]

          Run until program ends, hits a breakpoint or reaches line nnn}

The test suite

The test suite is absolutely amaze-balls because it’s very declarative. Uses therefore less brain-cycles and enables you to spend those on real problems.

it 'must leave on the same line by default' do
  enter 'next'
  debug_file('stepping') { $state.line.must_equal 10 }

And these are the main parts of byebug. Come back to get more content like this.

Hey you 👋 Want FREE resources to become the best developer and get a competitive edge? Subscribe!

Would you like to stay up to date on ? Subscribe here! I'll only use your email to keep u up to date on new technology and software development tips. It wont be shared. Feel free to unsubscribe anytime!