projects
/
pintos-anon
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
7a3a347
)
Fix typo.
author
Ben Pfaff
<blp@cs.stanford.edu>
Sun, 2 Jan 2005 00:04:20 +0000
(
00:04
+0000)
committer
Ben Pfaff
<blp@cs.stanford.edu>
Sun, 2 Jan 2005 00:04:20 +0000
(
00:04
+0000)
doc/debug.texi
patch
|
blob
|
history
diff --git
a/doc/debug.texi
b/doc/debug.texi
index cf8edc040029784e39feab449277678364e20cb5..12ca40ee3641017fffd269c40a10c25a3a8625c8 100644
(file)
--- 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
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}:
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}: