From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eliz@gnu.org>
Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10])
 by sourceware.org (Postfix) with ESMTPS id 1AF173834E45
 for <gdb-patches@sourceware.org>; Thu, 26 May 2022 06:52:05 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1AF173834E45
Received: from fencepost.gnu.org ([2001:470:142:3::e]:56866)
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1nu7Ln-00018w-TZ; Thu, 26 May 2022 02:52:03 -0400
Received: from [87.69.77.57] (port=1862 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1nu7Ln-0007PL-C0; Thu, 26 May 2022 02:52:03 -0400
Date: Thu, 26 May 2022 09:51:55 +0300
Message-Id: <83a6b4pz04.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@palves.net>
Cc: philippe.waroquiers@skynet.be, gdb-patches@sourceware.org
In-Reply-To: <ece793c3-98bc-213c-d165-14f926327f0b@palves.net> (message from
 Pedro Alves on Wed, 25 May 2022 23:18:02 +0100)
Subject: Re: [PATCH] gdb/manual: Introduce locspecs
References: <20220525193126.1613411-1-pedro@palves.net>
 <83mtf5perq.fsf@gnu.org> <0f341f7e-1eca-7087-495f-32f32fcc58e8@palves.net>
 <90766c666b0108ea2ab8d298c82dd9004af49ed7.camel@skynet.be>
 <ece793c3-98bc-213c-d165-14f926327f0b@palves.net>
X-Spam-Status: No, score=1.5 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH,
 DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF,
 RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6
X-Spam-Level: *
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 <gdb-patches.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-patches>,
 <mailto:gdb-patches-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-patches>,
 <mailto:gdb-patches-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2022 06:52:06 -0000

> Date: Wed, 25 May 2022 23:18:02 +0100
> Cc: gdb-patches@sourceware.org
> From: Pedro Alves <pedro@palves.net>
> 
> > IIUC, Eli would like to have location reserved for a breakpoint giving multiple resulting
> > locations.
> 
> No, he was saying he would prefer "location" to be reserved for location specifications,
> and to find a different name for breakpoint locations.

Yes.

> I don't see why would we even bother to consider renaming breakpoint
> locations to something else.

Because we want to use "location" for location specifications, and I
would like us to avoid a confusing ambiguity.