How to Read a Stack Trace

*
Accepted Session
Short Form
Beginner
Scheduled: Thursday, June 25, 2015 from 2:30 – 3:15pm in B301

Excerpt

When you're trying to make sense of an surprising software crash or an unexpected test failure, knowing your way around a stack trace can make the difference between bewildered frustration and finding a root cause.

Description

Come learn some skills that can make debugging a less frustrating, more successful experience!

When you’re trying to make sense of an surprising software crash or an unexpected test failure, knowing your way around a stack trace can make the difference between bewildered frustration and finding a root cause.

In this short talk, I’ll demonstrate some techniques for identifying the most important details of any stack trace, and for figuring out what they’re telling you. We’ll examine real stack traces from a few different languages, and follow them back to their causes. We’ll also learn how to recognize a few special situations where different rules apply.

Tags

debugging, stack trace, testing, crashes, bugs

Speaking experience

I've talked about Haskell at Open Source Bridge 2014, about Pair Programming at the Agile Conference (2010 and 2012) and the Agile Games conference, and about a handful of different topics at the Boston Software Craftsmanship meetup.

Speaker

  • Biography

    Moss lives in Boston, MA, where he works for Luminoso as a Python developer. His particular passion is working to make code so readable it invites people to use and change it. He has a growing interest in teaching development skills, and in finding ways to make the art of programming more inviting and accessible to newcomers.

    Sessions