From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 1trYL8/ljGIbEwgAWB0awg (envelope-from ) for ; Tue, 24 May 2022 10:03:59 -0400 Received: by simark.ca (Postfix, from userid 112) id B619C1E220; Tue, 24 May 2022 10:03:59 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=O4aIeiDb; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 021BB1E00D for ; Tue, 24 May 2022 10:03:59 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 441D7384F02A for ; Tue, 24 May 2022 14:03:58 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 441D7384F02A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1653401038; bh=A9BKvfrTqA+MB1GIHHtH9JfqjZ/7ssZayQyGUBfEqv0=; h=Date:To:In-Reply-To:Subject:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=O4aIeiDbYoqEZgALe2dfNNmYJlGWcjU18sF/dcGRCAiNOYs+xRMMrWUozRqvOZo0z PTDAnuWSo4TSb5UHdqGQ26s1Jl9VpRtTQwAJKc3DPUpzXZwrMEzMHH+LghvlVZgwaR T4iLg3xz6qeKf9PvKvOyeclsSRJ4my/bM5xc0Cwk= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 0A0D63857340 for ; Tue, 24 May 2022 14:03:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0A0D63857340 Received: from fencepost.gnu.org ([2001:470:142:3::e]:37206) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ntV8M-0004ZI-98; Tue, 24 May 2022 10:03:38 -0400 Received: from [87.69.77.57] (port=3538 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ntV8L-0000yI-IY; Tue, 24 May 2022 10:03:38 -0400 Date: Tue, 24 May 2022 17:03:25 +0300 Message-Id: <83bkvn58pe.fsf@gnu.org> To: Pedro Alves In-Reply-To: <45d7d87f-f78a-7c6b-28d7-285beecf9a8a@palves.net> (message from Pedro Alves on Tue, 24 May 2022 14:50:01 +0100) Subject: Re: [PATCH 0/2] info breakpoints improvements References: <20220519215552.3254012-1-pedro@palves.net> <70ddb0b0-7c7d-3bcd-ef3d-246290ae1edf@arm.com> <1e932144-4f4d-4c10-bbaa-deef05684895@palves.net> <83fskz5aol.fsf@gnu.org> <0247c63e-189d-0a71-8b5f-257fd83ff6a3@palves.net> <83czg359mz.fsf@gnu.org> <45d7d87f-f78a-7c6b-28d7-285beecf9a8a@palves.net> X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Eli Zaretskii via Gdb-patches Reply-To: Eli Zaretskii Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" > Date: Tue, 24 May 2022 14:50:01 +0100 > Cc: luis.machado@arm.com, gdb-patches@sourceware.org > From: Pedro Alves > > >> A location only breaks if it is enabled, _and_ its parent is enabled, so never. > > > > That's what I thought. But then why not "propagate" the "n" of the > > disabled breakpoint to all of its locations? > > Because then when you re-enable the parent breakpoint, you'd have lost the enabled/disabled > state of the individual locations. I don't understand why would that be lost. I'm not proposing to actually disable each location, I propose to _display_ them as disabled in that case. > > (gdb) info break 4.10 > > > > will show the truth, no? > > You can't "info break" an individual location. And you are certain we never will support that?