aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorJim Kingdon <jkingdon@engr.sgi.com>1993-10-27 05:48:39 +0000
committerJim Kingdon <jkingdon@engr.sgi.com>1993-10-27 05:48:39 +0000
commit66ad6ec894a4b1086cffc9514bd5fc1497c7d6d5 (patch)
tree125ec8befa059d16992285d96b55544cc973d739 /gdb
parente3b9a4856fb91e282fe52fff8b6e83a8e0367e70 (diff)
downloadgdb-66ad6ec894a4b1086cffc9514bd5fc1497c7d6d5.zip
gdb-66ad6ec894a4b1086cffc9514bd5fc1497c7d6d5.tar.gz
gdb-66ad6ec894a4b1086cffc9514bd5fc1497c7d6d5.tar.bz2
* remote.texi (Bootstrapping): Talk about getting the serial driver
to deal with ^C sent by gdb to stop the remote system.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/doc/remote.texi9
1 files changed, 6 insertions, 3 deletions
diff --git a/gdb/doc/remote.texi b/gdb/doc/remote.texi
index 350c52f..9073523 100644
--- a/gdb/doc/remote.texi
+++ b/gdb/doc/remote.texi
@@ -170,9 +170,12 @@ different name is used to allow you to distinguish the two if you wish.
If you want @value{GDBN} to be able to stop your program while it is
running, you need to use an interrupt-driven serial driver, and arrange
-for it to execute a breakpoint instruction when it receives a control C
-character. That is the character which @value{GDBN} uses to tell the
-remote system to stop.
+for it to stop when it receives a control C character (getting it to
+return the proper status to GDB probably requires changes to the
+standard stub; one quick and dirty way is to just execute a breakpoint
+instruction. @value{GDBN} will return a SIGTRAP instead of a SIGINT).
+That is the character which @value{GDBN} uses to tell the remote system
+to stop.
Other routines you need to supply are: