projects
/
pintos-anon
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
781c268
)
Wording.
author
Ben Pfaff
<blp@cs.stanford.edu>
Thu, 18 May 2006 19:47:04 +0000
(19:47 +0000)
committer
Ben Pfaff
<blp@cs.stanford.edu>
Thu, 18 May 2006 19:47:04 +0000
(19:47 +0000)
doc/debug.texi
patch
|
blob
|
history
diff --git
a/doc/debug.texi
b/doc/debug.texi
index e671b7495b2cc9a6e403abe6b252e1fa0ab24d35..27d4f260e72a93bf80ad926be5d1f942e23fa571 100644
(file)
--- a/
doc/debug.texi
+++ b/
doc/debug.texi
@@
-115,7
+115,7
@@
sense (e.g.@: function A is listed above function B, but B doesn't
call A), then it's a good sign that you're corrupting a kernel
thread's stack, because the backtrace is extracted from the stack.
Alternatively, it could be that the @file{kernel.o} you passed to
-@command{backtrace}
does not correspond to th
e kernel that produced
+@command{backtrace}
is not the sam
e kernel that produced
the backtrace.
Sometimes backtraces can be confusing without implying corruption.