projects
/
pintos-anon
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
567a7ff
)
fixed typo: "pass" should be "fail"
author
Godmar Back
<godmar@gmail.com>
Sun, 23 Sep 2007 15:40:23 +0000
(15:40 +0000)
committer
Godmar Back
<godmar@gmail.com>
Sun, 23 Sep 2007 15:40:23 +0000
(15:40 +0000)
doc/threads.texi
patch
|
blob
|
history
diff --git
a/doc/threads.texi
b/doc/threads.texi
index f1fd4dffbb0e4061be96b2104680a8f30ce13685..c1519e85a0df8774a0586c1c1a5d8da70ca0df66 100644
(file)
--- a/
doc/threads.texi
+++ b/
doc/threads.texi
@@
-633,7
+633,7
@@
does not actually mean that @func{pass} called @func{debug_panic}. In
fact, @func{fail} called @func{debug_panic} (via the @func{PANIC}
macro). GCC knows that @func{debug_panic} does not return, because it
is declared @code{NO_RETURN} (@pxref{Function and Parameter
fact, @func{fail} called @func{debug_panic} (via the @func{PANIC}
macro). GCC knows that @func{debug_panic} does not return, because it
is declared @code{NO_RETURN} (@pxref{Function and Parameter
-Attributes}), so it doesn't include any code in @func{
pass
} to take
+Attributes}), so it doesn't include any code in @func{
fail
} to take
control when @func{debug_panic} returns. This means that the return
address on the stack looks like it is at the beginning of the function
that happens to follow @func{fail} in memory, which in this case happens
control when @func{debug_panic} returns. This means that the return
address on the stack looks like it is at the beginning of the function
that happens to follow @func{fail} in memory, which in this case happens