Welcome back! This short lesson is our second on debugging strategies that will both help you with your project, and in your future as a software creator.
This lesson completes the checklist that we'll expect you to have followed before you receive help on the help site. But we also expect that, by following these steps, you'll find your mistakes faster, with less frustration, and needing less help from us. So let's get to it!
If you haven't already, check out the previous lesson on debugging for the first three steps in our checklist. To review, they are:
When you encounter an error in your program, frequently a piece of debugging output called a stack trace is generated. Here's an example drawn from the video walkthrough below:
Initially, this looks like a pretty intimidating mound of text! But, buried within are some incredibly useful nuggets of information. And by familiarizing yourself with stack traces and their contents, you can frequently at least figure out what is going wrong, and sometimes the solution as well. Let's explore how to read exception stack traces, and use them to understand what is going wrong with our code.
Next comes the part where the old geezer faculty member is going to tell you how to use the internets. Search? I can tell what you're thinking. Really? You're going to show me how to search the internet? I know how to do that!
I don't doubt it. But, nonetheless, I have a few tips that you might find useful.
That's all for this lesson! To recap, going forward, here are the steps that we'll expect you have to completed before you ask for help using the help site or forum:
Need more practice? Head over to the practice page.