aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorJohn Gilmore <gnu@cygnus>1992-06-21 01:56:05 +0000
committerJohn Gilmore <gnu@cygnus>1992-06-21 01:56:05 +0000
commit0cc37e2948c2b7adf4a1fb4c484e2183c9e30726 (patch)
treed7f916fea0dbc53dc7ed4cde02026ba18ab0c01e /gdb
parentd8a68b284492fdcc23ba412b03f00032e174413a (diff)
downloadgdb-0cc37e2948c2b7adf4a1fb4c484e2183c9e30726.zip
gdb-0cc37e2948c2b7adf4a1fb4c484e2183c9e30726.tar.gz
gdb-0cc37e2948c2b7adf4a1fb4c484e2183c9e30726.tar.bz2
Typo.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/doc/gdb.texinfo2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 3e8b55a..2efe198 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -4329,7 +4329,7 @@ On AMD 29000 family processors, registers are saved in a separate ``register
stack''. There is no way for GDB to determine the extent of this stack.
Normally, GDB just assumes that the stack is ``large enough''.
This may result in GDB referencing memory locations that don't
-exist, you can specify the ending address of the register stack with the
+exist, so you can specify the ending address of the register stack with the
@code{set rstack_high_address} command. The argument should be an address,
which you will probably want to precede with 0x and specify in hexadecimal.