From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] Change have_*_symbols functions to methods of program_space
Date: Fri, 13 Feb 2026 23:16:56 -0500 [thread overview]
Message-ID: <1d54a20a-fe14-4c67-92a4-20a3333cd84d@simark.ca> (raw)
In-Reply-To: <20260213-random-methods-v1-3-59bdac57c3e1@tromey.com>
> /* Prints the list of program spaces and their details on UIOUT. If
> REQUESTED is not -1, it's the ID of the pspace that should be
> printed. Otherwise, all spaces are printed. */
> diff --git a/gdb/progspace.h b/gdb/progspace.h
> index 3ed33b2e472..b3d8d6d39ed 100644
> --- a/gdb/progspace.h
> +++ b/gdb/progspace.h
> @@ -340,6 +340,18 @@ struct program_space
> it is not known. */
> CORE_ADDR entry_point_address () const;
>
> + /* Return true if any objfile of this program space has partial
> + symbols. */
> + bool have_partial_symbols ();
> +
> + /* Return true if any objfile of this program space has full
> + symbols. */
> + bool have_full_symbols ();
> +
> + /* Return true if any objfile of this program space has minimal
> + symbols. */
> + bool have_minimal_symbols ();
Maybe just a naming nit, I would s/have_/has_/ in the names. I feel
like it would read and sound better:
pspace->have_partial_symbols ()
vs
pspace->has_partial_symbols ()
Assuming that the pspace is the entity that "has" the symbols.
Simon
next prev parent reply other threads:[~2026-02-14 4:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 21:09 [PATCH 0/3] Change some " Tom Tromey
2026-02-13 21:09 ` [PATCH 1/3] Move entry point functions to program_space Tom Tromey
2026-02-13 21:09 ` [PATCH 2/3] Use std::optional in entry_point_address_query Tom Tromey
2026-02-13 21:09 ` [PATCH 3/3] Change have_*_symbols functions to methods of program_space Tom Tromey
2026-02-14 4:16 ` Simon Marchi [this message]
2026-02-14 17:33 ` Tom Tromey
2026-02-14 4:17 ` [PATCH 0/3] Change some " Simon Marchi
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=1d54a20a-fe14-4c67-92a4-20a3333cd84d@simark.ca \
--to=simark@simark.ca \
--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