Ask A Question

Notifications

You’re not receiving notifications from this thread.

Debugging: How to Interpret a Stacktrace Discussion

Scott Christensen 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!

Reply

Thanks Scott! 🍻

Reply

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.

Reply

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

Reply

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

Reply
catching up with the episodes. love this topic.
Reply

Hi,

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.

Thanks!

Reply

This was an amazing video

Reply

This was great! Loved the step by step debugging, learned about blame in github which is super valuable. Thanks!

Reply
Join the discussion

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

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

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

    Screencast tutorials to help you learn Ruby on Rails, Javascript, Hotwire, Turbo, Stimulus.js, PostgreSQL, MySQL, Ubuntu, and more. Icons by Icons8

    © 2023 GoRails, LLC. All rights reserved.