From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 45864 invoked by alias); 3 Oct 2017 17:15:46 -0000 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 Received: (qmail 45854 invoked by uid 89); 3 Oct 2017 17:15:45 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=naturally, ABC, abc X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 03 Oct 2017 17:15:44 +0000 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 1B558800A8; Tue, 3 Oct 2017 17:15:43 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 1B558800A8 Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=palves@redhat.com Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id 240996025E; Tue, 3 Oct 2017 17:15:39 +0000 (UTC) Subject: Re: [RFA v3] enable/disable sub breakpoint range To: Eli Zaretskii References: <83lgks1e1h.fsf@gnu.org> <834lrg198u.fsf@gnu.org> <815a1576-6a07-6a40-e887-9d886c4ada6c@redhat.com> <83zi98yxnr.fsf@gnu.org> Cc: roirand@adacore.com, gdb-patches@sourceware.org From: Pedro Alves Message-ID: <81b6ce9e-1ee0-1c60-81d4-869f7a9d6b5e@redhat.com> Date: Tue, 03 Oct 2017 17:15:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <83zi98yxnr.fsf@gnu.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2017-10/txt/msg00061.txt.bz2 On 10/03/2017 06:00 PM, Eli Zaretskii wrote: >> Cc: roirand@adacore.com, gdb-patches@sourceware.org >> From: Pedro Alves >> Date: Tue, 3 Oct 2017 17:40:45 +0100 >> >> (gdb) delete 1.3-5 4-5 >> >> I don't understand why you say you have to give them up. > > Because I now need to break a single range into several ranges. > > Wouldn't it be better to use 1.3-1.5 for the subranges, and then we > could still say 1.3-5 to mean all the breakpoints between 1.3 and 5? IMO, I'd rather not treat treat locations as decimals. If we supported that, then we'd naturally want to support 1.3-4.5 as well as meaning all locations from 1.3 to 4.5. I don't think that that's going to be a normal use case at all. Usually you'll set a breakpoint, and then look at the list of created locations and disable a few, all for the same breakpoint. Also, I think it'd be very confusing if we broke from how we treat sub ranges in other commands (such as thread ids). And also, if we ever come up with some object as is more than 2 levels deep, like e.g., A.B.C, then I think range specifiers like A.B.C1-C2 is much more friendly to type (and easier to implement) than A.B.C1-A.B.C2. Thanks, Pedro Alves