From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1720 invoked by alias); 22 Feb 2011 18:41:09 -0000 Received: (qmail 1711 invoked by uid 22791); 22 Feb 2011 18:41:08 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 Feb 2011 18:41:04 +0000 Received: (qmail 9125 invoked from network); 22 Feb 2011 18:41:02 -0000 Received: from unknown (HELO scottsdale.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 22 Feb 2011 18:41:02 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [RFA] info break/watch/trace use get_number_or_range, take two Date: Tue, 22 Feb 2011 18:41:00 -0000 User-Agent: KMail/1.13.5 (Linux/2.6.35-25-generic; KDE/4.6.0; x86_64; ; ) Cc: Michael Snyder , Eli Zaretskii References: <4D62E5E0.9080105@vmware.com> <4D64014A.1040306@vmware.com> In-Reply-To: <4D64014A.1040306@vmware.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201102221840.55311.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-02/txt/msg00616.txt.bz2 On Tuesday 22 February 2011 18:32:42, Michael Snyder wrote: > >> 2011-02-21 Michael Snyder > >> > >> * 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