Wordsmithing.

[pintos-anon] / doc / debug.texi

diff --git a/doc/debug.texi b/doc/debug.texi
index 8fbc7d53bd6b7bdcb16950754de7c47bd8fd70b5..bd1aa6af1c601a3e805573550e08a37e21df0b32 100644 (file)
--- a/doc/debug.texi
+++ b/doc/debug.texi
@@ -127,7 +127,7 @@ optimize such that an unrelated function C appears in the backtrace
 instead of A.  Function C is simply the function that happens to be in
 memory just after A.  In the threads project, this is commonly seen in
 backtraces for test failures; see @ref{The pass function fails, ,
-@func{pass} Fails}), for more information.
+@func{pass} Fails}, for more information.
 
 @menu
 * Backtrace Example::           
@@ -170,9 +170,9 @@ The backtrace output would then look something like this:
 0x8048ac8: ?? (??:0)
 @end example
 
-(You will probably not get the same results if you run the command above
-on your own kernel binary, because the source code you compiled from is
-different from the source code that panicked.)
+(You will probably not see exactly the same addresses if you run the
+command above on your own kernel binary, because the source code you
+compiled and the compiler you used are probably different.)
 
 The first line in the backtrace refers to @func{debug_panic}, the
 function that implements kernel panics.  Because backtraces commonly
@@ -314,6 +314,13 @@ a bug in the original Pintos code.  The first and second
 are quite likely, and you should seriously consider both.  We hope
 that the third is less likely, but it is also possible.
 
+@menu
+* Debugging User Programs::     
+@end menu
+
+@node Debugging User Programs
+@subsection Debugging User Programs
+
 You can also use @command{gdb} to debug a user program running under
 Pintos.  Start by issuing this @command{gdb} command to load the
 program's symbol table: