From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Observer mode
Date: Thu, 29 Apr 2010 17:54:00 -0000 [thread overview]
Message-ID: <834oiuxhyh.fsf@gnu.org> (raw)
In-Reply-To: <4BD9C057.9090805@codesourcery.com>
> Date: Thu, 29 Apr 2010 10:22:31 -0700
> From: Stan Shebs <stan@codesourcery.com>
>
> + @node Observation Mode
> + @subsection Observation Mode
A suitable index entry would be good here.
> + When all of these are set to @code{off}, then @value{GDBN} is said
> + to be @dfn{observation mode}.
"in observation mode", I presume.
Also, the above sentence is ambiguous: it took me a while to
understand that "all of these" refer to the settings described in this
section. Please say that explicitly.
> + combinations of these settings. For instance, if you have enabled
^^
Need two spaces here (and in a few other places in the patch).
> + @itemx set may-write-memory off
> + This controls whether @value{GDBN} will attempt to alter the contents
> + of memory, such as with assignment expressions in @code{print}.
This is also relevant to setting breakpoints, right? If so, I suggest
to mention them.
> + Otherwise, any sort of write attempt will result in an error."),
Is this useful behavior? I'd assume that setting these to off would
silently fail the operation. Otherwise, how would these settings be
useful? They exist to allow uninterrupted program run, don't they?
> + error ("No tracepoints downloaded, not starting trace");
No _() around a message here.
Thanks.
next prev parent reply other threads:[~2010-04-29 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 17:23 Stan Shebs
2010-04-29 17:54 ` Eli Zaretskii [this message]
2010-04-29 18:12 ` Michael Snyder
2010-04-30 3:19 ` Stan Shebs
2010-04-30 18:21 ` Tom Tromey
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=834oiuxhyh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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