Introduction

Tracking down and fixing both errors and unexpected behavior in your code is an inevitable part of being a developer. The art of finding the cause of problems and then fixing them in code is known as debugging. The origin of the term is a classic computer science tale worth reading if you haven’t already.

In this lesson, we’ll cover all of the main techniques you can use to debug your code when you run into a problem.

Learning Outcomes

By the end of this lesson, you should be able to do the following:

  • Describe what a stack trace is.
  • Explain how you can use a stack trace to debug your code.
  • Explain how you can use puts and Pry to debug your code.
  • Explain how you should decide to start with debugging.

Reading the Stack Trace

When your Ruby program crashes after encountering a runtime error or exception, it will produce a wall of text known as a stack trace that is then output in your terminal. A stack trace looks something like this:

sample stack trace

Don’t let the stack trace intimidate you. You don’t need to read it all or even know what most of it means.

The stack trace prints each line of code in your program that was executed before it crashed. The very first line of the stack trace will generally provide the most useful information about the error your program encountered:

first line of stack trace

First, this line of the stack trace will tell you what specific line caused the runtime error. In the above example, the error was encountered in line 30 of the file lib/bottles.rb. This line also provides a brief explanation of the error and the name of the error. (In this case, it’s a NameError). And yes, in Ruby, errors are also objects.

There you have it. The stack trace really is that simple. At this point, you know where in your code the exception is being raised, and you know the type of error you’re dealing with. You might even know what fixes need to be implemented in your code.

But what if you don’t know how to fix your code? Then it’s time to dive into debugging!

Debugging with puts

The debugging process is all about confirming assumptions about your code until you find something that goes against your assumptions. For example, does a variable or method return what you expect? Does a calculation or iteration over an array or hash give the output you expect?

The easiest and quickest way to confirm your assumptions while debugging is by using puts statements to output the return value of variables, methods, calculations, iterations, or even entire lines of code to your terminal.

Let’s say that for whatever reason, we need to write a method that takes a string and doubles each word in that string. Perhaps it’s a hostage situation that requires a pro debugger? Let’s take a look at a (simple) first draft:

def double_words_in_phrase(string)
  string_array = string.split(' ')
  string_array.map { |word| word * 2}
  string_array.join(' ')
end

double_words_in_phrase("This is a test")

#=> "This is a test"

Okay, that didn’t work. We didn’t expect that. The method didn’t throw an exception, so we don’t even have a line to start debugging at. Now what?

We know that string_array.join(' ') returns "This is a test" since it’s the last statement, so why not place a puts on the line before that to see what string_array is. As an alternative to puts, p is also commonly used for debugging; p is a combination of puts and inspect (more on that below). To better show the differences between what Ruby is printing to the terminal and returning, the examples in this section use the full IRB syntax, which is exactly what you’d see if you typed these commands into your own terminal IRB session.

irb(main):001:0> def double_words_in_phrase(string)
irb(main):002:1>   string_array = string.split(' ')
irb(main):003:1>   string_array.map { |word| word * 2}
irb(main):004:1>
irb(main):005:1>   p string_array
irb(main):006:1>
irb(main):007:1>   string_array.join(' ')
irb(main):008:1> end
=> :double_words_in_phrase

irb(main):009:0> double_words_in_phrase("This is a test")
["This", "is", "a", "test"]
=> "This is a test"

INTERESTING. Using p on string_array prints it to the console and shows us that the words aren’t doubled at all. Something must be wrong with how we called #map on string_array. For verification, let’s place another p statement before the map statement:

irb(main):001:0> def double_words_in_phrase(string)
irb(main):002:1>   string_array = string.split(' ')
irb(main):003:1>
irb(main):004:1>   p string_array
irb(main):005:1>
irb(main):006:1>   string_array.map { |word| word * 2}
irb(main):007:1>   p string_array
irb(main):008:1>   string_array.join(' ')
irb(main):009:1> end
=> :double_words_in_phrase

irb(main):010:0> double_words_in_phrase("This is a test")
["This", "is", "a", "test"]
["This", "is", "a", "test"]
=> "This is a test"

Indeed, we didn’t use #map correctly, as this particular method creates a new array rather than acting on the array it’s called on. Try running the above code in a REPL or IRB using #map! instead, and you’ll see the difference.

Hostage situation resolved! That wasn’t so bad, was it?

Debugging with puts and nil

Using puts is a great way to debug, but there’s a YUGE caveat with using it: calling puts on anything that is nil or an empty string or collection will just print a blank line to your terminal.

This is one instance where using p will yield more information. As mentioned above, p is a combination of puts and #inspect, the latter of which essentially prints a string representation of whatever it’s called on. To illustrate this, try the following in a REPL:

puts "Using puts:"
puts []
p "Using p:"
p []

Debugging with Pry

Pry is a Ruby gem that provides you with an interactive REPL while your program is running. The REPL provided by Pry is very similar to IRB but has added functionality.

To use Pry, you’ll first need to install it in your terminal by running gem install pry. You can then make it available in your program by requiring it at the top of your file with require 'pry'. Finally, to use Pry, you just need to call binding.pry at any point in your program.

To follow along with the Pry examples here, you have two options: 1. You can open up a new IRB session and type all of the code in there. When the code hits the binding.pry statement, it will essentially open an IRB session inside of your current IRB session. 2. You can save the code into a Ruby file (e.g., script.rb) and then run the file in your terminal (e.g., ruby script.rb). When the code hits the binding.pry statement, a new IRB-like session will open inside the terminal.

require 'pry'

def double_words_in_phrase(string)
  string_array = string.split(' ')

  binding.pry

  string_array.map { |word| word * 2}
  string_array.join(' ')
end

double_words_in_phrase("This is a test")

When your code executes and gets to binding.pry, it will open an IRB-like session in your terminal. You can then use that session to check the values of anything within the scope of where you included binding.pry. However, keep in mind that any code written after the binding.pry statement will not have been evaluated during the Pry session. Thus, adding a binding.pry line in our code is similar to creating a breakpoint in JavaScript.

To see this point in action, try running the following:

require 'pry'

def yell_greeting(string)
  name = string

  binding.pry

  name = name.upcase
  greeting = "WASSAP, #{name}!"
  puts greeting
end

yell_greeting("bob")

During the session, if you check for the value of name, you will notice that you get back the value bob instead of BOB. What value do you think greeting will return? Yup, it will be nil. This is because name = name.upcase and greeting = "WASSAP, #{name}!" occurred after the binding.pry call and were never evaluated.

As you can see, using Pry for debugging achieves the same outcome as puts debugging: it allows you to confirm the assumptions you have about particular parts of your code. If your code is complex, Pry will probably allow you to debug quicker thanks to its interactive runtime environment. In such scenarios, Pry will be easier to interact with than having to add puts statements everywhere and re-running your code each time.

There is far, far more that you can do with Pry, but that’s beyond the scope of this lesson. Check out the Assignments and Additional Resources to find out where you can learn more about this useful gem.

How to Start Debugging

Programs generally go wrong due to two main reasons:

  1. The program encounters an error and won’t run. For example, a typo may cause a syntax error to be raised that causes the program to crash. In this case, Ruby provides a stack trace.

  2. The program runs but does not work the way you expect. For example, you expect a method to return a 2, but it actually returns 6 when you run it. In this case, there is no stack trace.

Obviously, if available, the stack trace is the first place you should look when debugging. If there’s no stack trace, then puts and Pry are the easiest and quickest tools you can use to get yourself back up and running.

Assignment

  1. Go through the Ruby Guides Ruby Debugging tutorial, which covers everything about debugging in more depth.
  2. Read through the Exceptions and Stack Traces section of Launch School’s online book Introduction to Programming with Ruby.
  3. Download this repository and follow along with Part I of the Debugging with Pry tutorial. Keep this repository, because Part II will be completed during the ruby testing section.

Additional Resources

This section contains helpful links to other content. It isn’t required, so consider it supplemental for if you need to dive deeper into something.

Knowledge Check

This section contains questions for you to check your understanding of this lesson. If you’re having trouble answering the questions below on your own, review the material above to find the answer.

  • What is a stack trace?
  • What is generally the most useful line in a stack trace?
  • What are the two things you can learn from the first line of a stack trace?
  • How do puts and Pry help you in the debugging process?
  • What should you use instead of puts for nil values?
  • Where should you start with debugging if you encounter a runtime error?
  • Where should you start with debugging if your program runs but does not work the way you expect?
Improve this lesson on GitHub

Have a question?

Chat with our friendly Odin community in our Discord chatrooms!

Open Discord