projects
/
pintos-anon
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
0ba9f00
)
removed trailing whitespace
author
Godmar Back
<godmar@gmail.com>
Wed, 5 Nov 2008 04:53:26 +0000
(23:53 -0500)
committer
Godmar Back
<godmar@gmail.com>
Wed, 5 Nov 2008 04:53:26 +0000
(23:53 -0500)
doc/userprog.texi
patch
|
blob
|
history
diff --git
a/doc/userprog.texi
b/doc/userprog.texi
index d3a70c810f7eb10e0b9823bb0fb82b3b962dbf59..9d80e375669819c5a43da14ae4009c85f7d344f8 100644
(file)
--- a/
doc/userprog.texi
+++ b/
doc/userprog.texi
@@
-639,8
+639,8
@@
following conditions is true:
@item
@var{pid} does not refer to a direct child of the calling process.
@var{pid} is a direct child of the calling process if and
@item
@var{pid} does not refer to a direct child of the calling process.
@var{pid} is a direct child of the calling process if and
-only if the calling process received @var{pid} as a return value
-from a successful call to @code{exec}.
+only if the calling process received @var{pid} as a return value
+from a successful call to @code{exec}.
Note that children are not inherited: if @var{A} spawns child @var{B}
and @var{B} spawns child process @var{C}, then @var{A} cannot wait for
Note that children are not inherited: if @var{A} spawns child @var{B}
and @var{B} spawns child process @var{C}, then @var{A} cannot wait for
@@
-650,11
+650,11
@@
a new parent if their parent process exits before they do.
@item
The process that calls @code{wait} has already called @code{wait} on
@item
The process that calls @code{wait} has already called @code{wait} on
-@var{pid}. That is, a process may wait for any given child at most
+@var{pid}. That is, a process may wait for any given child at most
once.
@end itemize
once.
@end itemize
-Processes may spawn any number of children, wait for them in any order,
+Processes may spawn any number of children, wait for them in any order,
and may even exit without having waited for some or all of their children.
Your design should consider all the ways in which waits can occur.
All of a process's resources, including its @struct{thread}, must be
and may even exit without having waited for some or all of their children.
Your design should consider all the ways in which waits can occur.
All of a process's resources, including its @struct{thread}, must be