From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA] info break/watch/trace use get_number_or_range, take two
Date: Tue, 22 Feb 2011 18:41:00 -0000 [thread overview]
Message-ID: <201102221840.55311.pedro@codesourcery.com> (raw)
In-Reply-To: <4D64014A.1040306@vmware.com>
On Tuesday 22 February 2011 18:32:42, Michael Snyder wrote:
> >> 2011-02-21 Michael Snyder <msnyder@vmware.com>
> >>
> >> * gdb.texinfo (Set Breaks): Add @dots{} to arguments of info break.
> >> (Set Watchpoints): Add @dots{} to argument of info watchpoints.
> >> (Listing Tracepoints): Add @dots{} to argument of info tracepoints.
> >
> > This part is okay, but didn't we decide to add an explanation of
> > ranges, as in "24-42"?
>
> I think so, although I see that discussion as unfinished.
> The question is, where to put it and how to refer to it?
It's on my queue to document the "disable display" change.
Of course, if someone wants to do that for me, I certainly
don't mind.
"thread apply" has blurb mentioning ranges like that:
It can be a single thread number, one of the numbers
shown in the first field of the @samp{info threads} display; or it
could be a range of thread numbers, as in @code{2-4}.
That looks pretty clear to me. I was thinking on borrowing it.
Or were you thinking of something more detailed?
--
Pedro Alves
prev parent reply other threads:[~2011-02-22 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 23:00 Michael Snyder
2011-02-22 9:27 ` Pedro Alves
2011-02-22 10:56 ` Eli Zaretskii
2011-02-22 18:32 ` Michael Snyder
2011-02-22 18:48 ` Eli Zaretskii
2011-02-22 19:02 ` Michael Snyder
2011-02-22 18:31 ` Michael Snyder
2011-02-22 11:49 ` Eli Zaretskii
2011-02-22 18:33 ` Michael Snyder
2011-02-22 18:41 ` Pedro Alves [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=201102221840.55311.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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