From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, uweigand@de.ibm.com,
pedro_alves@portugalmail.pt
Subject: Re: [rfc] Shared libraries over the remote protocol, take two
Date: Mon, 18 Jun 2007 20:05:00 -0000 [thread overview]
Message-ID: <uzm2xqbdo.fsf@gnu.org> (raw)
In-Reply-To: <20070618150211.GA23415@caradoc.them.org> (message from Daniel Jacobowitz on Mon, 18 Jun 2007 11:02:11 -0400)
> Date: Mon, 18 Jun 2007 11:02:11 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Ulrich Weigand <uweigand@de.ibm.com>, Pedro Alves <pedro_alves@portugalmail.pt>
>
> Index: gdb/NEWS
> ===================================================================
> --- gdb/NEWS.orig 2007-06-18 10:15:05.000000000 -0400
> +++ gdb/NEWS 2007-06-18 10:15:14.000000000 -0400
This is fine, thanks.
> --- gdb/doc/gdb.texinfo.orig 2007-06-18 10:15:05.000000000 -0400
> +++ gdb/doc/gdb.texinfo 2007-06-18 10:15:14.000000000 -0400
This is also fine, but...
> +The currently defined stop reasons are:
> +
> +@itemize @bullet
> +@item
> +If @var{n} is @samp{watch}, @samp{rwatch}, or @samp{awatch}, then the
> +packet indicates a watchpoint hit, and @var{r} is the data address, in
> +hex.
> +
> +@item
> +@cindex shared library events, remote reply
> +If @var{n} is @samp{library}, then the packet indicates that the
> +loaded libraries have changed. @value{GDBN} should use
> +@samp{qXfer:libraries:read} to fetch a new list of loaded libraries.
> +@var{r} is ignored.
> +@end itemize
I think using @itemize and conditional sentences like this is not the
very elegant and concise way of saying things. Compare with this
alternative:
The currently defined stop reasons are:
@table @samp
@item watch
@itemx rwatch
@itemx awatch
The packet indicates a watchpoint hit, and @var{r} is the data address, in
hex.
@cindex shared library events, remote reply
@item library
The packet indicates that the loaded libraries have changed.
@value{GDBN} should use @samp{qXfer:libraries:read} to fetch a new
list of loaded libraries. @var{r} is ignored.
@end table
I think this is better, as it makes the stop reasons stand out in a
more clear way. Do you agree?
next prev parent reply other threads:[~2007-06-18 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 15:02 Daniel Jacobowitz
2007-06-18 19:32 ` Jim Blandy
2007-06-18 19:38 ` Daniel Jacobowitz
2007-06-18 22:04 ` Jim Blandy
2007-06-18 22:20 ` Daniel Jacobowitz
2007-06-18 20:05 ` Eli Zaretskii [this message]
2007-07-02 19:03 ` Daniel Jacobowitz
2007-06-18 20:10 ` Jim Blandy
2007-06-18 20:13 ` Jim Blandy
2007-06-18 20:33 ` Daniel Jacobowitz
2007-06-18 22:06 ` Jim Blandy
2007-06-18 21:13 ` Pedro Alves
2007-07-02 22:01 ` Daniel Jacobowitz
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=uzm2xqbdo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
--cc=uweigand@de.ibm.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