From f6d77b49fb7e4bab34c7fa4dc1ae9cd307231e23 Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Sun, 2 Jan 2005 00:04:20 +0000 Subject: [PATCH] Fix typo. --- doc/debug.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/debug.texi b/doc/debug.texi index cf8edc0..12ca40e 100644 --- a/doc/debug.texi +++ b/doc/debug.texi @@ -256,7 +256,7 @@ backtrace kernel.o Call stack: 0xc0106eff 0xc01102fb 0xc010dc22 You can run the Pintos kernel under the supervision of the @command{i386-elf-gdb} debugger.@footnote{If you're using an 80@var{x}86 system for development, it's probably just called -@command{addr2line}.} There are two steps in the process. First, +@command{gdb}.} There are two steps in the process. First, start Pintos with the @option{--gdb} option, e.g.@: @command{pintos --gdb run}. Second, in a second terminal, invoke @command{gdb} on @file{kernel.o}: -- 2.30.2