From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f50.google.com (mail-wr1-f50.google.com [209.85.221.50]) by sourceware.org (Postfix) with ESMTPS id 72F983857340 for ; Tue, 24 May 2022 13:50:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 72F983857340 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=palves.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wr1-f50.google.com with SMTP id f2so25851523wrc.0 for ; Tue, 24 May 2022 06:50:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=lEQaBeEiZgHpUXIo6zjI8Xfnwrc5JkWQE4JPCWJyrho=; b=kT/D4yQ+OyHvxlJsKAIaJLhX93dI4gJ0ZGp1HHLHgiBSsJ5xYEDKWLJGntUcOD2F2S 8krrYjgZrTfaEOo1oDVXiYhHyPgv9bQibiuYlYlxbNTAwlgm3c4gEsROzcVvtPCQ8PpW DQ5T5uRQtH2AQh8caHpJEy76eFMM+SxeZ2H/BL2PMtis2kcymfr7rbI2T1ZIf+kjQkwP HM6KCM1P6kFg8uOgsMMtWRl6s7kQ0qDKk/qgyoZ7UXZCv5End1rSX3DxXdPLhGa90D/8 EKO8omCyw/goHyvjy3cwhvwS9rhKbS6F+dBoA/TPnZ66XZP653h3QKe/nUERD1rhEPAq rAQQ== X-Gm-Message-State: AOAM533KEA7mbpAWkvXlEds6KklsdOIyO4dtoElL70gC3WKdeFnZYUcy eY3qArZmV+QzCG/q9YK1kGE= X-Google-Smtp-Source: ABdhPJwG6gzeDiYy2GXsTTC1jNHqQC+V7JGI6NzwMYId2xLsLBjRSAhUM/EFQq9ctkrW1R2aMwchFQ== X-Received: by 2002:a5d:5885:0:b0:20f:f390:c47e with SMTP id n5-20020a5d5885000000b0020ff390c47emr2366967wrf.133.1653400203421; Tue, 24 May 2022 06:50:03 -0700 (PDT) Received: from ?IPV6:2001:8a0:f924:2600:209d:85e2:409e:8726? ([2001:8a0:f924:2600:209d:85e2:409e:8726]) by smtp.gmail.com with ESMTPSA id c13-20020adfc04d000000b0020fee88d0f2sm2918963wrf.0.2022.05.24.06.50.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 24 May 2022 06:50:02 -0700 (PDT) Message-ID: <45d7d87f-f78a-7c6b-28d7-285beecf9a8a@palves.net> Date: Tue, 24 May 2022 14:50:01 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCH 0/2] info breakpoints improvements Content-Language: en-US To: Eli Zaretskii Cc: luis.machado@arm.com, gdb-patches@sourceware.org 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> From: Pedro Alves In-Reply-To: <83czg359mz.fsf@gnu.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.6 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org 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: , X-List-Received-Date: Tue, 24 May 2022 13:50:06 -0000 On 2022-05-24 14:43, Eli Zaretskii wrote: >> Date: Tue, 24 May 2022 14:29:27 +0100 >> Cc: luis.machado@arm.com, gdb-patches@sourceware.org >> From: Pedro Alves >> >> On 2022-05-24 14:20, Eli Zaretskii wrote: >>>> Date: Tue, 24 May 2022 11:02:07 +0100 >>>> From: Pedro Alves >>>> >>>> Note how breakpoint 4 is disabled, but since all the locations are enabled, the "n" doesn't stand out all that much. >>> >>> I'm confused: what is the meaning of having a breakpoint disabled, >>> while all of its locations are enabled? Under which conditions will >>> such a breakpoint break? >>> >> >> 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. It's like, if you turn off the mains switch in your home, the individual light switches in each room stay in their positions. And you can flip on/off the individual switches before turning on the mains too. That way > > (gdb) info break 4.10 > > will show the truth, no? You can't "info break" an individual location. > > I also wonder whether we should display something special on the > "header row" instead of "y" or "n" when some of the locations are > enabled and others aren't. How about "p" (for "partial") or maybe > "y/n"? > That may be useful, yes.