From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: RTe: Location Specs (Was: [pushed v5] gdb/manual: Introduce location specs)
Date: Thu, 02 Jun 2022 19:37:15 +0300 [thread overview]
Message-ID: <83leufdnt0.fsf@gnu.org> (raw)
In-Reply-To: <3b5161b4-9fcb-193b-d5ef-7762eac850f0@palves.net> (message from Pedro Alves on Thu, 2 Jun 2022 14:44:31 +0100)
> Date: Thu, 2 Jun 2022 14:44:31 +0100
> Cc: gdb-patches@sourceware.org
> From: Pedro Alves <pedro@palves.net>
>
> > 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.
Thanks, I made those changes and pushed.
prev parent reply other threads:[~2022-06-02 16:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 19:42 [PATCH v4] gdb/manual: Introduce location specs Pedro Alves
2022-05-27 14:16 ` Eli Zaretskii
2022-05-27 15:04 ` Pedro Alves
2022-05-27 15:52 ` Eli Zaretskii
2022-05-27 17:11 ` Pedro Alves
2022-05-27 17:31 ` Eli Zaretskii
2022-05-27 17:51 ` Pedro Alves
2022-05-27 18:23 ` Eli Zaretskii
2022-05-27 18:42 ` Pedro Alves
2022-05-27 18:50 ` Pedro Alves
2022-05-27 19:00 ` Eli Zaretskii
2022-05-27 19:30 ` Pedro Alves
2022-05-28 7:43 ` Eli Zaretskii
2022-05-30 14:38 ` Pedro Alves
2022-05-27 18:55 ` Eli Zaretskii
2022-05-27 19:05 ` Pedro Alves
2022-05-27 19:14 ` Eli Zaretskii
2022-05-27 19:17 ` Pedro Alves
2022-05-27 19:34 ` Eli Zaretskii
2022-05-27 19:38 ` Pedro Alves
2022-05-28 7:39 ` Eli Zaretskii
2022-05-30 14:44 ` [pushed v5] " Pedro Alves
2022-05-30 16:15 ` Eli Zaretskii
2022-05-31 11:05 ` [PATCH] Improve clear command's documentation Pedro Alves
2022-05-31 12:36 ` Eli Zaretskii
2022-05-31 13:04 ` Pedro Alves
2022-05-31 13:42 ` Eli Zaretskii
2022-05-31 14:47 ` Pedro Alves
2022-05-31 16:06 ` Eli Zaretskii
2022-05-31 11:13 ` [PATCH] Explicitly mention yet-unloaded shared libraries in location spec examples Pedro Alves
2022-05-31 11:47 ` Eli Zaretskii
2022-05-31 11:17 ` [pushed v5] gdb/manual: Introduce location specs Pedro Alves
2022-05-31 11:31 ` [PATCH] Improve break-range's documentation Pedro Alves
2022-05-31 11:55 ` Eli Zaretskii
2022-05-31 12:03 ` Pedro Alves
2022-05-31 12:09 ` Eli Zaretskii
2022-06-01 17:17 ` RTe: Location Specs (Was: [pushed v5] gdb/manual: Introduce location specs) Eli Zaretskii
2022-06-02 11:10 ` Pedro Alves
2022-06-02 11:49 ` Eli Zaretskii
2022-06-02 12:40 ` Pedro Alves
2022-06-02 12:56 ` Eli Zaretskii
2022-06-02 13:44 ` Pedro Alves
2022-06-02 16:37 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83leufdnt0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).