aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2000-05-07 10:57:54 +0000
committerEli Zaretskii <eliz@gnu.org>2000-05-07 10:57:54 +0000
commit502d24d454123c6bb60132a5ebcbe04094b8a1e2 (patch)
tree94879250f30d8dc4c5279559b6dbbbba6cfb0eee /gdb
parentd68fc559381163a8bb213ef5e93f6c6a2a47352b (diff)
downloadgdb-502d24d454123c6bb60132a5ebcbe04094b8a1e2.zip
gdb-502d24d454123c6bb60132a5ebcbe04094b8a1e2.tar.gz
gdb-502d24d454123c6bb60132a5ebcbe04094b8a1e2.tar.bz2
Typo correction, again from Brian Youmans.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/mi/gdbmi.texinfo9
1 files changed, 4 insertions, 5 deletions
diff --git a/gdb/mi/gdbmi.texinfo b/gdb/mi/gdbmi.texinfo
index e6f0d9e..c2aad45 100644
--- a/gdb/mi/gdbmi.texinfo
+++ b/gdb/mi/gdbmi.texinfo
@@ -2075,11 +2075,10 @@ Regular stepping:
@end example
Asynchronous command. Resumes the inferior which executes one machine
-instruction. The output, once stop, will vary depend on whether we have
-@c Someone who knows this should figure out what 'once stop' is supposed
-@c to be. 'once stop is reached'? - BTY
-stopped in the middle of a source line or not. In the former case, the
-address at which the program stopped will be printed as well.
+instruction. The output, once GDB has stopped, will vary depending on
+whether we have stopped in the middle of a source line or not. In the
+former case, the address at which the program stopped will be printed as
+well.
@subsubheading GDB Command