From: Pedro Alves <pedro@palves.net>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] Move decode_location to code_breakpoint
Date: Mon, 30 May 2022 16:42:09 +0100 [thread overview]
Message-ID: <d1dc45f1-c2a1-838d-eb2f-ed5a1ec2fa07@palves.net> (raw)
In-Reply-To: <20220528024231.474534-4-tom@tromey.com>
On 2022-05-28 03:42, Tom Tromey wrote:
> diff --git a/gdb/breakpoint.h b/gdb/breakpoint.h
> index 5ce6edf6efc..663c939c162 100644
> --- a/gdb/breakpoint.h
> +++ b/gdb/breakpoint.h
> @@ -709,16 +709,6 @@ struct breakpoint
> /* Print to FP the CLI command that recreates this breakpoint. */
> virtual void print_recreate (struct ui_file *fp) const;
>
> - /* Given the location (second parameter), this method decodes it and
> - returns the SAL locations related to it. For ordinary
> - breakpoints, it calls `decode_line_full'. If SEARCH_PSPACE is
> - not NULL, symbol search is restricted to just that program space.
> -
> - This function is called inside `location_to_sals'. */
> - virtual std::vector<symtab_and_line> decode_location
> - (struct event_location *location,
> - struct program_space *search_pspace);
> -
> /* Return true if this breakpoint explains a signal. See
> bpstat_explains_signal. */
> virtual bool explains_signal (enum gdb_signal)
> @@ -882,12 +872,19 @@ struct code_breakpoint : public breakpoint
> const address_space *aspace,
> CORE_ADDR bp_addr,
> const target_waitstatus &ws) override;
> - std::vector<symtab_and_line> decode_location
> - (struct event_location *location,
> - struct program_space *search_pspace) override;
>
> protected:
>
> + /* Given the location (second parameter), this method decodes it and
I've noticed that "second" here got stale when this was first
converted to a method. I think we should just remove the parenthetical
remark and be done with it. Would you mind doing that while at it?
The patch looks OK, regardless.
Pedro Alves
> + returns the SAL locations related to it. For ordinary
> + breakpoints, it calls `decode_line_full'. If SEARCH_PSPACE is
> + not NULL, symbol search is restricted to just that program space.
> +
> + This function is called inside `location_to_sals'. */
> + virtual std::vector<symtab_and_line> decode_location
> + (struct event_location *location,
> + struct program_space *search_pspace);
> +
> /* Helper method that does the basic work of re_set. */
> void re_set_default ();
>
next prev parent reply other threads:[~2022-05-30 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 2:42 [PATCH 0/3] More minor breakpoint cleanups Tom Tromey
2022-05-28 2:42 ` [PATCH 1/3] Change breakpoint_re_set_default to a method Tom Tromey
2022-05-30 15:32 ` Pedro Alves
2022-05-28 2:42 ` [PATCH 2/3] Change location_to_sals " Tom Tromey
2022-05-30 15:32 ` Pedro Alves
2022-06-01 4:50 ` Tom Tromey
2022-06-01 16:38 ` Pedro Alves
2022-06-10 21:34 ` Tom Tromey
2022-06-13 14:36 ` Pedro Alves
2022-08-14 0:44 ` Tom Tromey
2022-05-28 2:42 ` [PATCH 3/3] Move decode_location to code_breakpoint Tom Tromey
2022-05-30 15:42 ` Pedro Alves [this message]
2022-08-14 0:41 ` Tom Tromey
2022-08-14 0:45 ` [PATCH 0/3] More minor breakpoint cleanups Tom Tromey
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=d1dc45f1-c2a1-838d-eb2f-ed5a1ec2fa07@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).