All threads / Debugging: How to Interpret a Stacktrace Discussion

Ask A Question


You鈥檙e not receiving notifications from this thread.

Debugging: How to Interpret a Stacktrace Discussion

Scott Christensen

Thanks, Chris. You consistently put out amazing content that I don't see anyone else doing. I appreciate the quality of your lessons. Keep up the awesomeness!


Hello Chris, This stuff is important! Especially when your back is against the wall. You should consider doing an entire series on debugging :) Good work.

Agreed! Any other debugging topics you'd like to see?

I use byebug all the time to slow the program down and examine the state. That is an important tool. How to use it effectively, e.g., conditional break points, goes a long way in being able to fix runtime crashes or bugs.

I agree. I thinks some more videos on debugging would be awesome!


Thanks, Chris. That's a super helpful video!
One thing I noticed was that you look at the docs for Rails 5 ( and since the stack trace is from a Rails 3 version it's better to look at the corresponding docs, i.e.
Often they are the same, but sometimes the differences can catch you out.

catching up with the episodes. love this topic.


I have a little bit different debugging question from anything I have seen addressed. I was wondering if you know of a way to determine all the places javascript methods are being called from? The project I am working on is a disorganized and large mess and determining the process flow in JavaScript has been pretty difficult.


Join the discussion

Want to stay up-to-date with Ruby on Rails?

Join 52,887+ developers who get early access to new tutorials, screencasts, articles, and more.

    We care about the protection of your data. Read our Privacy Policy.

    logo Created with Sketch.

    Ruby on Rails tutorials, guides, and screencasts for web developers learning Ruby, Rails, Javascript, Turbolinks, Stimulus.js, Vue.js, and more. Icons by Icons8

    © 2021 GoRails, LLC. All rights reserved.