From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id ULgFJ5SYj2JThQgAWB0awg (envelope-from ) for ; Thu, 26 May 2022 11:11:16 -0400 Received: by simark.ca (Postfix, from userid 112) id 8EB0F1E220; Thu, 26 May 2022 11:11:16 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI, NICE_REPLY_A,RDNS_DYNAMIC 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 F1CE91E01D for ; Thu, 26 May 2022 11:11:15 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 46FE1385736B for ; Thu, 26 May 2022 15:11:15 +0000 (GMT) Received: from mail-wm1-f45.google.com (mail-wm1-f45.google.com [209.85.128.45]) by sourceware.org (Postfix) with ESMTPS id C9C183858CDA for ; Thu, 26 May 2022 15:11:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C9C183858CDA 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-wm1-f45.google.com with SMTP id 67-20020a1c1946000000b00397382b44f4so1256948wmz.2 for ; Thu, 26 May 2022 08:11:01 -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=RMDvi2JGDSDmgn0LIewWjnX2I1ZqeIX4wW5C9P+oOz0=; b=EV3Hp/om+PlOxdIO5SiiZv54vt3aH+XDCDVoc5gKV5xOkRJurEnL8LlrTG6uTzITsW bmMAyqAn+AdICPyuOldG0ywoyVcfrbkKMmwSOe0BByE1+/+zF+k3duQW/mdcSY2cj2XC zOT66wK3MzQwBBpw2LaYrKGE1cPsIBdI9jOPZzZkUi2fnIkBbw1BMzY/voDLKxFL0Yai jvvRScLWY4x211D/OFQIVZEMlovmkEIAAvxgkjha1ZYVEM5Ebq3y6FhX9hCE+4Gz57t5 lD5b5hr0r2yOemHK3JsgyZ8+1Owhr1aq9QHGBTB2LDing4lCZUlMUA0aaLxC2CeDaY4X Fljg== X-Gm-Message-State: AOAM532qZD7G6rmQo3E5zd0jkkMxMFyFoRUoBMkY//VgsRTTkkckpn8E 4YevVwNtXbjPH3LnLm2tJQdfLX5JHxk= X-Google-Smtp-Source: ABdhPJxkmlDQD+URD283Hn2FRrHhsrNCdb1bvVD/Y1Y2ooEP3fbXF+zqHVCDQm8b0Y7YQY/h24A7DQ== X-Received: by 2002:a05:600c:500a:b0:397:4044:cb2e with SMTP id n10-20020a05600c500a00b003974044cb2emr2841305wmr.28.1653577860638; Thu, 26 May 2022 08:11:00 -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 n7-20020a05600c500700b00395f15d993fsm5828005wmr.5.2022.05.26.08.10.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 26 May 2022 08:10:59 -0700 (PDT) Message-ID: <141778c2-4367-db68-41d2-716efc95e4d1@palves.net> Date: Thu, 26 May 2022 16:10:58 +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 v2 1/2] Always show locations for breakpoints & show canonical location spec Content-Language: en-US To: Eli Zaretskii References: <20220519215552.3254012-1-pedro@palves.net> <20220519215552.3254012-2-pedro@palves.net> <834k1kd7ne.fsf@gnu.org> <625057b2-1691-a472-fa93-0dabacbddd39@palves.net> <83ilpv5bd3.fsf@gnu.org> <4c7a9504-83e0-6c02-fda6-0254ab4eede4@palves.net> <8335gwpiih.fsf@gnu.org> <83v8tsnxp6.fsf@gnu.org> From: Pedro Alves In-Reply-To: <83v8tsnxp6.fsf@gnu.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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: , Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 2022-05-26 16:03, Eli Zaretskii wrote: > Where does it call them that? in the GDB source code? That's not very > relevant for the manual: we don't use variable names in the manual, > and readers of the manual don't necessarily read the GDB source code. > So we need to find good terminology for the manual. No, in error messages, in online help, and, importantly, the manual has been very clearly calling them breakpoint locations, so every user that refers to the "1.1", "1.2", etc., things calls them the breakpoint locations. (top-gdb) disable 2.3 Bad breakpoint location number '3' Anyhow, I can't reply to your message in detail right now, but I would like to say that I will try to document locations vs locations specs better and then send a v4, when I have a chance.