From: Godmar Back Date: Mon, 8 Jan 2007 08:46:49 +0000 (+0000) Subject: - removed @ref to "printf Reboots" since this no longer applies and the @anchor is... X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=884d659ef4a594017bc5a456b772fc82fa3e6b76;p=pintos-anon - removed @ref to "printf Reboots" since this no longer applies and the @anchor is gone - fixed typo print -> printf --- diff --git a/doc/debug.texi b/doc/debug.texi index 0d5a79d..958e51b 100644 --- a/doc/debug.texi +++ b/doc/debug.texi @@ -21,13 +21,12 @@ introduces you to a few of them. Don't underestimate the value of @func{printf}. The way @func{printf} is implemented in Pintos, you can call it from practically anywhere in the kernel, whether it's in a kernel thread or -an interrupt handler, almost regardless of what locks are held (but see -@ref{printf Reboots} for a counterexample). +an interrupt handler, almost regardless of what locks are held. @func{printf} is useful for more than just examining data. It can also help figure out when and where something goes wrong, even when the kernel crashes or panics without a useful error message. The -strategy is to sprinkle calls to @func{print} with different strings +strategy is to sprinkle calls to @func{printf} with different strings (e.g.@: @code{"<1>"}, @code{"<2>"}, @dots{}) throughout the pieces of code you suspect are failing. If you don't even see @code{<1>} printed, then something bad happened before that point, if you see @code{<1>}