From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] MI Doco
Date: Fri, 09 Jun 2006 19:07:00 -0000 [thread overview]
Message-ID: <ubqt2qhc5.fsf@gnu.org> (raw)
In-Reply-To: <17538.8607.697546.427486@kahikatea.snap.net.nz> (message from Nick Roberts on Sun, 4 Jun 2006 11:56:15 +1200)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sun, 4 Jun 2006 11:56:15 +1200
> Cc: gdb-patches@sources.redhat.com
>
> Here's a patch.
Thanks; comments below. You can commit after you take care of them.
> ! For the developers convenience CLI commands can be entered directly.
"entered directly" is not clear. How about this:
For developers' convenience, GDB/MI supports CLI commands even
without @code{-interpreter-exec}.
> ! However, CLI commands that use sequences of commands such @code{source},
> ! @code{commands} will not work
I don't understand from this text what will not work. (Please enclose
input that would be typed by user in @kbd, btw.) Do you mean if I
type "source, commands", it will not work? Or do you mean something
else?
Also, you are missing "as" after "such", I think.
> and commands that result in queries such
> ! as pending breakpoints and quitting once execution has started will
> ! default to yes.
"..commands that query the user will behave as if the user replied yes."
> ! target. This is only present when GDB's event loop
Please use @value{GDBN} instead a literal "GDB".
> is truely asynchronous which is currently only the case for remote targets.
You mean "truly", I think.
Also, there should be a comma after "asynchronous".
> + @smallexample
> + -> -break-insert main
> + <- ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
> + enabled="y",addr="0x08048564",func="main",file="myprog.c",
> + fullname="/home/nickrob/myprog.c",line="68",times="0"@}
> + <- (gdb)
Please use "(@value{GDBP})" instead of a literal "(gdb)".
> + not been implemented yet and these are labelled N.A.@: (not available).
^^^^^^^^
"labeled"
> ! Executes one machine instruction. If the instruction is a function
> ! call continues until the function returns. If the program stops at an
^
A comma needed here.
> + @subheading @value{GDBN} Command
> +
> + The corresponding @value{GDBN} command is @samp{set inferior-tty /dev/pts/1}.
I think you should have only "set inferior-tty" in the @samp, the
argument is just an example of the command's usage, and thus doesn't
belong here.
next prev parent reply other threads:[~2006-06-09 19:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 0:23 Nick Roberts
2006-06-02 9:05 ` Eli Zaretskii
2006-06-02 10:23 ` Nick Roberts
2006-06-02 10:44 ` Eli Zaretskii
2006-06-03 23:57 ` Nick Roberts
2006-06-04 19:32 ` Eli Zaretskii
2006-06-09 19:07 ` Eli Zaretskii [this message]
2006-06-09 19:12 ` Daniel Jacobowitz
2006-06-09 19:52 ` Eli Zaretskii
2006-06-09 19:57 ` Daniel Jacobowitz
2006-06-10 7:32 ` Eli Zaretskii
2006-07-01 12:35 ` [commit] Fix MI prompt in manual (was: MI Doco) Eli Zaretskii
2006-06-09 19:58 ` [PATCH] MI Doco Bob Rossi
2006-06-09 23:27 ` Nick Roberts
2006-06-10 7:51 ` Eli Zaretskii
2006-06-10 21:40 ` Nick Roberts
2006-06-11 3:31 ` Eli Zaretskii
2006-06-11 10:47 ` Nick Roberts
2006-06-11 19:27 ` Eli Zaretskii
2006-06-11 21:42 ` Nick Roberts
2006-06-12 3:36 ` Eli Zaretskii
2006-06-12 6:19 ` Nick Roberts
2006-06-13 3:39 ` Eli Zaretskii
2006-06-13 4:46 ` Nick Roberts
2006-06-13 17:26 ` Eli Zaretskii
2006-06-13 21:15 ` Nick Roberts
2006-06-14 18:30 ` Eli Zaretskii
2006-06-14 21:05 ` Nick Roberts
2006-06-15 6:56 ` Eli Zaretskii
2006-06-30 2:13 ` Nick Roberts
2006-06-30 12:09 ` Eli Zaretskii
2006-06-30 14:12 ` 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=ubqt2qhc5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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