From: Eli Zaretskii <eliz@gnu.org>
To: Russell Shaw <rjshaw@netspace.net.au>
Cc: gdb@sourceware.org, gdb-patches@sources.redhat.com
Subject: [commit] Clarify "monitor" command (was: [RFC] plugin/extension interface)
Date: Sat, 03 Dec 2005 12:49:00 -0000 [thread overview]
Message-ID: <u64q6s5w0.fsf@gnu.org> (raw)
In-Reply-To: <43912C55.7090708@netspace.net.au> (message from Russell Shaw on Sat, 03 Dec 2005 16:25:41 +1100)
> Date: Sat, 03 Dec 2005 16:25:41 +1100
> From: Russell Shaw <rjshaw@netspace.net.au>
> Cc: gdb@sourceware.org
>
> It would be useful if the manual actually said that this is the way to
> add new commands for an external monitor. It is bad when i can only learn
> new things about gdb by complaining.
Thank you for pointing this out. I've just committed the following
change to the GDB manual:
2005-12-03 Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo (Connecting): Explain that `monitor' is a way to
extend GDB with commands for external monitor.
Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.298
diff -u -r1.298 gdb.texinfo
--- gdb/doc/gdb.texinfo 2 Dec 2005 11:44:19 -0000 1.298
+++ gdb/doc/gdb.texinfo 3 Dec 2005 12:42:11 -0000
@@ -11966,10 +11966,15 @@
another target.
@cindex send command to remote monitor
+@cindex extend @value{GDBN} for remote targets
+@cindex add new commands for external monitor
@kindex monitor
@item monitor @var{cmd}
-This command allows you to send commands directly to the remote
-monitor.
+This command allows you to send arbitrary commands directly to the
+remote monitor. Since @value{GDBN} doesn't care about the commands it
+sends like this, this command is the way to extend @value{GDBN}---you
+can add new commands that only the external monitor will understand
+and implement.
@end table
@node Server
next prev parent reply other threads:[~2005-12-03 12:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 18:25 [RFC] plugin/extension interface Andrew STUBBS
2005-12-02 18:49 ` Eli Zaretskii
2005-12-02 19:23 ` Daniel Jacobowitz
2005-12-02 19:36 ` Mark Kettenis
2005-12-02 22:12 ` Jim Blandy
2005-12-02 22:16 ` Daniel Jacobowitz
2005-12-02 22:41 ` Mark Kettenis
2005-12-02 23:07 ` Jim Blandy
2005-12-02 23:13 ` Bob Rossi
2005-12-02 23:32 ` Daniel Jacobowitz
2005-12-03 0:57 ` Jim Blandy
2005-12-03 2:32 ` Daniel Jacobowitz
2005-12-03 2:41 ` Bob Rossi
2005-12-03 2:41 ` Russell Shaw
2005-12-03 2:45 ` Daniel Jacobowitz
2005-12-03 3:13 ` Russell Shaw
2005-12-03 3:33 ` Daniel Jacobowitz
2005-12-03 4:05 ` Russell Shaw
2005-12-03 4:14 ` Daniel Jacobowitz
2005-12-03 4:44 ` Russell Shaw
2005-12-03 4:49 ` Daniel Jacobowitz
2005-12-03 5:25 ` Russell Shaw
2005-12-03 12:49 ` Eli Zaretskii [this message]
2005-12-03 12:51 ` [commit] Clarify "monitor" command Russell Shaw
2005-12-03 16:08 ` [commit] Clarify "monitor" command (was: [RFC] plugin/extension interface) Daniel Jacobowitz
2005-12-03 5:06 ` [RFC] plugin/extension interface Russell Shaw
2005-12-03 5:12 ` Daniel Jacobowitz
2005-12-03 9:29 ` Eli Zaretskii
2005-12-03 9:50 ` Russell Shaw
2005-12-03 9:57 ` Eli Zaretskii
2005-12-05 16:17 ` Andrew STUBBS
2005-12-05 16:34 ` Bob Rossi
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=u64q6s5w0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sourceware.org \
--cc=rjshaw@netspace.net.au \
/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