How to Read a Stack Trace
summary
Explains how to locate the real fault: the innermost frame usually shows where it breaks, but languages differ — Python shows outermost first while Ruby and Java start at the inside — and frameworks like Flask/Sinatra/Spring produce a lot of ignorable noise. Covers nested exceptions, test failures (assertion line vs root cause), and concrete tactics: start inside, move out until code with your project name appears, reproduce locally, add logging, simplify lines, and write a unit test or clearer exception message so the next trace is useful.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:37Why practice reading stack traces?
- 3:26Plan
- 5:05How do you read a stack trace?
- 8:54Where did it break?
- 9:45Language Matters
- 12:32Where did you call it?
- 15:48How did you get there?
- 19:28Learn what to ignore!
- 21:38Harder Cases
- 23:49Nested Errors
- 26:31Running Tests
- 29:29What went wrong?
- 34:15How can you test that?
- 38:04Questions?
related talks
29mPeering into the black box: tips for visualizing your program's behavior
58mDebugging #Java
47mHow to Debug - Lessons Learnt from 10 Years of Spring Boot
37mPrying Open The Black Box
42mDissecting Ruby with Ruby
57mHow to Debug Lessons Learnt From 10 Years of #SpringBoot
38mSpelunking in Ruby
54mDebugging Effectively