From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f53.google.com (mail-wr1-f53.google.com [209.85.221.53]) by sourceware.org (Postfix) with ESMTPS id BDACE38376D2 for ; Thu, 2 Jun 2022 13:44:34 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org BDACE38376D2 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-f53.google.com with SMTP id t6so6544687wra.4 for ; Thu, 02 Jun 2022 06:44:34 -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=2EmnB9vSoAbGblpEFtAczG6hDRXjOVQes3TVyxe7rGw=; b=prtxeqDq4K1azPPpUvAEe+eT32HcPJDn7G1TuQZ0MFXCWLUma6afZJmmv3+6mgfwpu EXoGCYH0rfmxek6GXXdt9RP87NkqB8lKT4doGrOE8dJVGJzmoKka8cK/fuAyeaprBFOE bMRkgGN/eUB8hejVTWoqhacDYW9xE9d1YATJ1J0oUhitTMWQSfcnZ7BVW67mlvn4RNSw RperUTMyvm9oaLdPvXDRUIFffi7biJ2IfanK+qXBptaF2B/KTXJhKvnI1EtA7vVmAgHB SRLtFRw2QYYQL7LMBsPqs4k2zhB0AFRFY1EgVU4BxaGPiUHXZYVzvgk1tUIdUsW/xXpK tpCQ== X-Gm-Message-State: AOAM533EO2u4LSORWMUCJ2BQIZHpo86qx6VYGLy4tzjSm1OV9vrQlzLO 6eRfMGQ3XRiIpIwhdaxZuc1oVDzUcQg= X-Google-Smtp-Source: ABdhPJwX01s+Z2nYBAAzenQBezUAXiCXasBXM3Rr2v829scM8jU9CV+6HYcLqcvwA+t2SzqlI3TWLA== X-Received: by 2002:a5d:6d88:0:b0:210:3bd9:172f with SMTP id l8-20020a5d6d88000000b002103bd9172fmr3765374wrs.246.1654177473557; Thu, 02 Jun 2022 06:44:33 -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 t22-20020a05600c41d600b00397550b387bsm6411171wmh.23.2022.06.02.06.44.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 02 Jun 2022 06:44:32 -0700 (PDT) Message-ID: <3b5161b4-9fcb-193b-d5ef-7762eac850f0@palves.net> Date: Thu, 2 Jun 2022 14:44:31 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: RTe: Location Specs (Was: [pushed v5] gdb/manual: Introduce location specs) Content-Language: en-US To: Eli Zaretskii Cc: gdb-patches@sourceware.org References: <20220526194250.2310460-1-pedro@palves.net> <838rqmm7gb.fsf@gnu.org> <6914f754-4e33-5aa1-4ea6-dca9504e8bfe@palves.net> <83wne0fgmd.fsf@gnu.org> <834k13ffpf.fsf@gnu.org> <5eb11c4f-a35a-79fa-cc67-0428dc88134a@palves.net> <83wndzdy08.fsf@gnu.org> From: Pedro Alves In-Reply-To: <83wndzdy08.fsf@gnu.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.2 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: Thu, 02 Jun 2022 13:44:36 -0000 On 2022-06-02 13:56, Eli Zaretskii wrote: >> Date: Thu, 2 Jun 2022 13:40:10 +0100 >> Cc: gdb-patches@sourceware.org >> From: Pedro Alves >> >> The original text before my changes used "specifies": >> >> Several @value{GDBN} commands accept arguments that specify a location >> of your program's code. Since @value{GDBN} is a source-level >> debugger, a location usually specifies some line in the source code. >> Locations may be specified using three different formats: >> linespec locations, explicit locations, or address locations. >> >> and I wanted to extend it to give the function name, address, label, etc. examples, >> other attributes one can specify. >> >> I don't recall exactly how I got to "indicate". To me, in something >> like "-line LINENUM", LINENUM is the line indicated in the spec. In >> "-function FUNC", FUNC is the function name indicated in the spec. >> I think I was just trying to avoid the repetition in "a specification specifies", >> which sounds like it was a mistake, as it introduced ambiguity. Better to >> go back to "specifies". > > OK, how about this instead? > > Several @value{GDBN} commands accept arguments that specify a location > or locations of your program's code. Many times locations are > specified using a source line number, but they can also be specified > by a function name, an address, a label, etc. The different > forms of specifying a location that @value{GDBN} recognizes are > collectively known as forms of @dfn{location specification}, or > @dfn{location spec}. This section documents the forms of specifying > locations that @value{GDBN} recognizes. Perfect. > >>>>> For a C@t{++} constructor, the @value{NGCC} compiler generates several >>>>> -instances of the function body, used in different cases. >>>>> +instances of the function body, used in different cases, but their >>>>> +source-level names are identical, unless you qualify them. >>>> >>>> What do you mean by "qualify" here? >>> >>> The "fully-qualified and prototyped function" part. >> >> That's unrelated to what is being alluded to here. > > OK, I will drop the "unless you qualify them" part. Sounds good.