From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: documentation change for ambiguous linespec patch
Date: Tue, 15 Nov 2011 16:57:00 -0000 [thread overview]
Message-ID: <83fwhpe36s.fsf@gnu.org> (raw)
In-Reply-To: <m3mxbypfq1.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Date: Mon, 14 Nov 2011 14:16:22 -0700
>
> To my surprise, the ambiguous linespec change mostly makes gdb accord
> better with the existing documentation. So, I did not need many changes
> to the documentation.
>
> Here is what I propose.
Thanks.
> +* GDB now handles ambiguous linespecs more consistently; the existing
> + FILE:LINE support has been expanded to other types of linespecs. A
> + breakpoint will now have locations at all the matching points in all
How about "...will now be set on all matching locations..."? "Have
locations" sounds a bit confusing; at least I never thought of a
breakpoint as _having_ a location.
> + locations will be added or subtracted according to
> + inferior changes.
Will these additions and removals be announced by GDB? If so, perhaps
an example or a note to that effect is in order.
Also, is "subtracted" the right word here? I use it only as an
arithmetic operation, but I'm not a native speaker.
The rest is (trivially) fine with me. Thanks.
next prev parent reply other threads:[~2011-11-15 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 21:16 Tom Tromey
2011-11-15 16:57 ` Eli Zaretskii [this message]
2011-11-15 18:05 ` Tom Tromey
2011-11-15 18:18 ` Eli Zaretskii
2011-11-15 18:24 ` 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=83fwhpe36s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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