aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc
diff options
context:
space:
mode:
authorDaniel Jacobowitz <drow@false.org>2008-02-28 16:26:18 +0000
committerDaniel Jacobowitz <drow@false.org>2008-02-28 16:26:18 +0000
commit8edfe2693228f91b78661dc04e8c91095ab19487 (patch)
treeeedbb500de71648048b63f651ab5b3b13aeb07d4 /gdb/doc
parent0d6ba1b16e08532da8a7fa2de4d867927cf3f9f6 (diff)
downloadbinutils-8edfe2693228f91b78661dc04e8c91095ab19487.zip
binutils-8edfe2693228f91b78661dc04e8c91095ab19487.tar.gz
binutils-8edfe2693228f91b78661dc04e8c91095ab19487.tar.bz2
* infcmd.c (kill_if_already_running): Make static. Use
target_require_runnable. * target.c (target_require_runnable): New. * target.h (target_require_runnable): Declare. * gdb.texinfo (Starting): Mention always-running targets. (Target Commands): Add an anchor for load. (Connecting): Explain continue instead of run.
Diffstat (limited to 'gdb/doc')
-rw-r--r--gdb/doc/ChangeLog6
-rw-r--r--gdb/doc/gdb.texinfo21
2 files changed, 23 insertions, 4 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 1cc9af4..95d94d9 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,9 @@
+2008-02-28 Daniel Jacobowitz <dan@codesourcery.com>
+
+ * gdb.texinfo (Starting): Mention always-running targets.
+ (Target Commands): Add an anchor for load.
+ (Connecting): Explain continue instead of run.
+
2008-02-27 Daniel Jacobowitz <dan@codesourcery.com>
* gdb.texinfo (Debugging Output): Document "set debug timestamp".
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 4f4b694..dfc6e81 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -1818,8 +1818,19 @@ argument to @value{GDBN} (@pxref{Invocation, ,Getting In and Out of
If you are running your program in an execution environment that
supports processes, @code{run} creates an inferior process and makes
-that process run your program. (In environments without processes,
-@code{run} jumps to the start of your program.)
+that process run your program. In some environments without processes,
+@code{run} jumps to the start of your program. Other targets,
+like @samp{remote}, are always running. If you get an error
+message like this one:
+
+@smallexample
+The "remote" target does not support "run".
+Try "help target" or "continue".
+@end smallexample
+
+@noindent
+then use @code{continue} to run your program. You may need @code{load}
+first (@pxref{load}).
The execution of a program is affected by certain information it
receives from its superior. @value{GDBN} provides ways to specify this
@@ -12669,6 +12680,7 @@ Show the current status of displaying communications between
@kindex load @var{filename}
@item load @var{filename}
+@anchor{load}
Depending on what remote debugging facilities are configured into
@value{GDBN}, the @code{load} command may be available. Where it exists, it
is meant to make @var{filename} (an executable) available for debugging
@@ -12847,8 +12859,9 @@ program has already exited, this will have no effect.)
@end table
Once the connection has been established, you can use all the usual
-commands to examine and change data and to step and continue the
-remote program.
+commands to examine and change data. The remote program is already
+running; you can use @kbd{step} and @kbd{continue}, and you do not
+need to use @kbd{run}.
@cindex interrupting remote programs
@cindex remote programs, interrupting