From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id WQbCKfofkWIYuwgAWB0awg (envelope-from ) for ; Fri, 27 May 2022 15:01:14 -0400 Received: by simark.ca (Postfix, from userid 112) id 99D0F1E221; Fri, 27 May 2022 15:01:14 -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=FrUcwtwA; 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 22C4F1E01D for ; Fri, 27 May 2022 15:01:14 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id B5A103828333 for ; Fri, 27 May 2022 19:01:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B5A103828333 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1653678073; bh=AXpVZW+ITZgzU9BJvBx1R6N4BInnj6DIlFlY1xZu9TM=; 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=FrUcwtwAXczV2qwJroQvQz8lCUJtj/XDYrSD7XCzQbib1Tnd6maMaNtTgXrlnmazf QoSDr4T2FKdO4lcZkJTzQ+n7mgekKG4mLVsDalTMkHeBN3Es+T+SS8BPBUV732gg+X JrO3+1yLScj/pD7IFqQDqH3tQiEjR0du2sp4wP5E= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id D3A4E3828928 for ; Fri, 27 May 2022 19:00:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D3A4E3828928 Received: from fencepost.gnu.org ([2001:470:142:3::e]:37318) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nufCe-0002Yv-TD; Fri, 27 May 2022 15:00:53 -0400 Received: from [87.69.77.57] (port=4313 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 1nufCJ-0003Jo-8q; Fri, 27 May 2022 15:00:52 -0400 Date: Fri, 27 May 2022 22:00:27 +0300 Message-Id: <83mtf2n6lw.fsf@gnu.org> To: Pedro Alves In-Reply-To: (message from Pedro Alves on Fri, 27 May 2022 19:50:58 +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> 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 19:50:58 +0100 > From: Pedro Alves > Cc: gdb-patches@sourceware.org > > BTW, my text says this: > > +The location spec may be incomplete, and @value{GDBN} will do its best > +to find all the locations in the program that match it. For example, > +a location spec may just indicate a line number and a source filename > ^^^^^^^^^^^^^^^ > +with no directory components, > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > and this example too: > > +@item > +The location spec specifies a file name, and multiple files in the > +program share the same name. That's about location specs; I was talking about the code location, where the missing attributes need to be resolved. > IMO, from this it should be obvious that the code location has directory > components that you can match. I don't think I follow: match with what and in what way? Are you talking about "matching" of an absolute file name with relative file names? > The explicit locations section already says for example: > > @table @code > @item -source @var{filename} > The value specifies the source file name. To differentiate between > files with the same base name, prepend as many directories as is necessary > to uniquely identify the desired file, e.g., @file{foo/bar/baz.c}. Otherwise > @value{GDBN} will use the first file it finds with the given base > name. This option requires the use of either @code{-function} or @code{-line}. > > I'm not sure we want to go into details like that in the intro section. Users won't > be able to use any location spec format without reading the corresponding section, > so they'll see this. 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.