From: Ben Pfaff Date: Sat, 1 Jan 2005 03:35:08 +0000 (+0000) Subject: Add another pointer to the debugging documentation. X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=19df3c4b3fe74917695b4557f98393fbf35193e9;p=pintos-anon Add another pointer to the debugging documentation. --- diff --git a/EXPERIENCE b/EXPERIENCE index 76231d1..078fb9a 100644 --- a/EXPERIENCE +++ b/EXPERIENCE @@ -16,10 +16,6 @@ Threads project: - Students don't understand that they'll need to read lots of code before they can start writing. - - Students don't read the debugging documentation. Point out in - multiple places, and especially point to the backtrace - description. - - Students think data structures are more important than they really are. Say that clever data structures won't get you too much extra credit compared to simpler ones. Really bad or "stupid" data diff --git a/doc/threads.texi b/doc/threads.texi index 8e6e38d..dae47bb 100644 --- a/doc/threads.texi +++ b/doc/threads.texi @@ -401,6 +401,15 @@ This is less likely to produce surprises, because everyone can see everyone else's code as it is written, instead of just when it is finished. These systems also make it possible to review changes and, when a change introduces a bug, drop back to working versions of code. + +@item +You should expect to run into bugs that you simply don't understand +while working on this and subsequent projects. When you do, go back +and reread the appendix on debugging tools, which is filled with +useful debugging tips that should help you to get back up to speed +(@pxref{Debugging Tools}). Be sure to read the section on backtraces +(@pxref{Backtraces}), which will help you to get the most out of every +kernel panic or assertion failure. @end itemize @node Problem 1-1 Alarm Clock