From: Pedro Alves <pedro@palves.net>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 1/7] event_location -> location_spec
Date: Mon, 30 May 2022 16:02:20 +0100 [thread overview]
Message-ID: <5e7ce942-7e60-b965-a85a-5a9d72a71db9@palves.net> (raw)
In-Reply-To: <88650019deedbf4192af4cf3e2a9acba6828c6b6.camel@skynet.be>
On 2022-05-28 11:08, Philippe Waroquiers wrote:
> On Fri, 2022-05-27 at 19:02 +0100, Pedro Alves wrote:
>> Currently, GDB internally uses the term "location" for both the
>> location specification the user input (linespec, explicit location, or
>> an address location), and for actual resolved locations, like the
>> breakpoint locations, or the result of decoding a location spec to
>> SaLs. This is expecially confusing in the breakpoints module, as
>> struct breakpoint has these two fields:
> FWIW, I think that the introduction of location spec in the manual and in
> the code is a nice improvement/clarification.
> Thanks for Pedro and Eli hard work on this.
Thanks!
>
> A small question:
> In GDB, when I do
> (gdb) apropos -v location
> possibly some occurrences of "location" might be changed by "locspec"
> or "location specification".
> (e.g. in 'help breakpoint/break-range/disassemble/strace/...'
> and I have not seen that the patches are modifying this online help.
Yeah, I was waiting until the manual changes landed. I will look into that as
a separate patch.
> Also, is the constant #define LOCATION_HELP_STRING
> not better called LOCATION_SPEC_HELP_STRING ?
Indeed. I've done that change locally.
next prev parent reply other threads:[~2022-05-30 15:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 18:02 [PATCH 0/7] location -> location spec Pedro Alves
2022-05-27 18:02 ` [PATCH 1/7] event_location -> location_spec Pedro Alves
2022-05-28 10:08 ` Philippe Waroquiers
2022-05-30 15:02 ` Pedro Alves [this message]
2022-05-27 18:02 ` [PATCH 2/7] Eliminate the two-level data structures behind location_specs Pedro Alves
2022-05-30 15:09 ` Pedro Alves
2022-05-27 18:02 ` [PATCH 3/7] Eliminate copy_location_spec Pedro Alves
2022-05-27 18:02 ` [PATCH 4/7] Convert location_spec_empty_p to a method Pedro Alves
2022-05-27 18:02 ` [PATCH 5/7] Convert location_spec_type " Pedro Alves
2022-05-27 18:02 ` [PATCH 6/7] Convert location_spec_to_string " Pedro Alves
2022-05-27 18:02 ` [PATCH 7/7] Convert set_location_spec_string " Pedro Alves
2022-05-30 15:20 ` Pedro Alves
2022-06-15 19:47 ` [PATCH 0/7] location -> location spec Tom Tromey
2022-06-17 9:24 ` Pedro Alves
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=5e7ce942-7e60-b965-a85a-5a9d72a71db9@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
/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).