From: Andrew Cagney <ac131313@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [patch] Missing menu entries for Remote Debugging chapte
Date: Mon, 21 Jan 2002 15:24:00 -0000 [thread overview]
Message-ID: <3C4CA312.1000706@cygnus.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 107 bytes --]
Oops,
Missed this when moving the remote debugging stuff to its own chapter.
I've checked it in.
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1674 bytes --]
2002-01-21 Andrew Cagney <ac131313@redhat.com>
* gdb.texinfo (Remote Debugging): Create a menu.
(Top): Add ``Remote Debugging'' to menu.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.77
diff -u -r1.77 gdb.texinfo
--- gdb.texinfo 2002/01/21 18:56:05 1.77
+++ gdb.texinfo 2002/01/21 23:21:34
@@ -137,6 +137,7 @@
* Altering:: Altering execution
* GDB Files:: @value{GDBN} files
* Targets:: Specifying a debugging target
+* Remote Debugging:: Debugging remote programs
* Configurations:: Configuration-specific information
* Controlling GDB:: Controlling @value{GDBN}
* Sequences:: Canned sequences of commands
@@ -192,6 +193,7 @@
* Altering:: Altering execution
* GDB Files:: @value{GDBN} files
* Targets:: Specifying a debugging target
+* Remote Debugging:: Debugging remote programs
* Configurations:: Configuration-specific information
* Controlling GDB:: Controlling @value{GDBN}
* Sequences:: Canned sequences of commands
@@ -9942,6 +9944,13 @@
@node Remote Debugging
@chapter Debugging remote programs
+
+@menu
+* Server:: Using the gdbserver program
+* NetWare:: Using the gdbserve.nlm program
+* remote stub:: Implementing a remote stub
+* Protocol:: Communication protocol
+@end menu
@node Server
@section Using the @code{gdbserver} program
next reply other threads:[~2002-01-21 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 15:24 Andrew Cagney [this message]
2002-01-22 0:54 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C4CA312.1000706@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox