summaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.base
diff options
context:
space:
mode:
authorJim Blandy <jimb@codesourcery.com>2007-12-26 17:11:16 +0000
committerJim Blandy <jimb@codesourcery.com>2007-12-26 17:11:16 +0000
commit7968d5e9e9ee3d3fded159b798f8035244378b18 (patch)
tree6dd87624478ff7221d2f1c74b438be307a19981e /gdb/testsuite/gdb.base
parenta7aa6e1d738cc4df6bec67d65fed95185471b72d (diff)
downloadgdb-7968d5e9e9ee3d3fded159b798f8035244378b18.tar.gz
* gdb.base/multi-forks.exp: Doc fix.
Diffstat (limited to 'gdb/testsuite/gdb.base')
-rw-r--r--gdb/testsuite/gdb.base/multi-forks.exp11
1 files changed, 8 insertions, 3 deletions
diff --git a/gdb/testsuite/gdb.base/multi-forks.exp b/gdb/testsuite/gdb.base/multi-forks.exp
index 7161be583f2..b607d43d76d 100644
--- a/gdb/testsuite/gdb.base/multi-forks.exp
+++ b/gdb/testsuite/gdb.base/multi-forks.exp
@@ -53,9 +53,14 @@ global gdb_prompt
# parent and child of multiple Unix fork() system calls.
#
-# Inferior program calls fork 4 times. Since each fork
-# calls fork 4 times, there will be 16 forks. Each fork
-# saves the return values of its own 4 fork calls.
+# The inferior program builds a tree of processes by executing a loop
+# four times, calling fork at each iteration. Thus, at each
+# iteration, the total number of processes doubles; after four
+# iterations, we have 16 processes. Each process saves the results
+# from its 'fork' calls, so we can tell which leaf a given process is
+# by looking at which forks returned zero and which returned a pid: a
+# zero means to take the child's branch; a pid means to take the
+# parent's branch.
# First set gdb to follow the child.
# The result should be that each of the 4 forks returns zero.