From: Eli Zaretskii <eliz@gnu.org>
To: Samuel Bronson <naesten@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: suggestions for node "(gdb)Set Watchpoints"
Date: Tue, 09 Jun 2009 03:46:00 -0000 [thread overview]
Message-ID: <E1MDsHr-0006O0-N3@fencepost.gnu.org> (raw)
In-Reply-To: <db65a1cd0906081230x74a5d8b8l295fb86efec4e1a6@mail.gmail.com> (message from Samuel Bronson on Mon, 8 Jun 2009 15:30:20 -0400)
> Date: Mon, 8 Jun 2009 15:30:20 -0400
> From: Samuel Bronson <naesten@gmail.com>
> Cc: gdb@sourceware.org
>
> This paragraph does make things a lot better, but at the same time
> makes it even stranger that the other paragraph is so far away from
> the description of what kinds of expressions to watch. I think the
> other paragraph should be moved up to be with this one -- probably
> after it.
Thanks, I will look into how this section could be re-arranged
better. Please understand, however, that it is impossible to move
everything to the beginning of the section. Most manual sections do
not include unimportant information, so it could be a tough choice.
The reader is assumed to read the text in its entirety, not just the
first couple of paragraphs.
> It would also be nice to have a more in-depth description of exactly
> which watchpoint-related events GDB is actually able to intercept.
Please elaborate. Unless I misunderstand what you mean, we already
describe this in depth.
prev parent reply other threads:[~2009-06-09 3:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 19:30 Samuel Bronson
2009-06-09 3:46 ` Eli Zaretskii [this message]
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=E1MDsHr-0006O0-N3@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=naesten@gmail.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