From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id +DxzFqHSkWKM0ggAWB0awg (envelope-from ) for ; Sat, 28 May 2022 03:43:29 -0400 Received: by simark.ca (Postfix, from userid 112) id 574411E221; Sat, 28 May 2022 03:43:29 -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=jVfFfQ+c; 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=-3.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.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 E87A51E00D for ; Sat, 28 May 2022 03:43:28 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 3A7F83857365 for ; Sat, 28 May 2022 07:43:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3A7F83857365 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1653723808; bh=OYIXZtxS0+8nUuAPaF+23T7gG1IvjdFmox52cvw7s54=; 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=jVfFfQ+cxe2fULsxBHcCm8dsonfhLH1ul0kUNWHht4hPAHiZe6cdvAUURWwP9Z7gy VTTaIPWfn8a4B6f+EVTONq42Qcxy50W+peIjb3XRrmT6LWxUBStdNDQ58vsBOGcs4O 2Ku5XIyj/W6zXWW9ZkLrso8j5JdZ2JhZusnZnYMs= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id DC5063857B9B for ; Sat, 28 May 2022 07:43:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DC5063857B9B Received: from fencepost.gnu.org ([2001:470:142:3::e]:53256) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nur6K-0005NY-He; Sat, 28 May 2022 03:43:08 -0400 Received: from [87.69.77.57] (port=3427 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 1nur6J-0003qP-T6; Sat, 28 May 2022 03:43:08 -0400 Date: Sat, 28 May 2022 10:43:05 +0300 Message-Id: <837d66m7au.fsf@gnu.org> To: Pedro Alves In-Reply-To: <266eba78-e6c7-c72a-4820-bbbabe37ac04@palves.net> (message from Pedro Alves on Fri, 27 May 2022 20:30:06 +0100) Subject: Re: [PATCH v4] gdb/manual: Introduce location specs References: <20220526194250.2310460-1-pedro@palves.net> <8335gvnjrw.fsf@gnu.org> <956e1fbd-5f03-c021-c390-82e1cf3493b5@palves.net> <83wne7m0ri.fsf@gnu.org> <2bc9b5c9-879a-2848-16f4-6cfd796563a8@palves.net> <83sfounaqw.fsf@gnu.org> <02a46873-35dc-0d9c-1890-292b807d9484@palves.net> <83pmjyn8as.fsf@gnu.org> <113bd07c-3bfe-0780-50a9-4c41c84942e9@palves.net> <83mtf2n6lw.fsf@gnu.org> <266eba78-e6c7-c72a-4820-bbbabe37ac04@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: Fri, 27 May 2022 20:30:06 +0100 > Cc: gdb-patches@sourceware.org > From: Pedro Alves > > On 2022-05-27 20:00, Eli Zaretskii wrote: > > > What I was talking about was not about using the location specs, it > > was about explaining what it is and how it differs from the code > > location. I think we have to explain the terminology before we use > > it, since it is not entirely trivial. > > OK, here's what I added on top of v4, locally. WDYT? LGTM, so I think this can go in, given the results of my review of the rest of the patch (see my other message) are taken care of. I will re-read this section after the changes are pushed, and decide whether any additional clarifications are needed; if so, I will make those changes later. Thanks.