From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Christina Schimpe <christina.schimpe@intel.com>
Cc: gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: [PATCH v4 03/13] gdb: Add get_main_func_start_pc to refactor frame.c:inside_main_func.
Date: Thu, 03 Sep 2026 06:53:28 +0000 [thread overview]
Message-ID: <87fqzqsu53.fsf@linaro.org> (raw)
In-Reply-To: <20260708143639.2214689-4-christina.schimpe@intel.com> (Christina Schimpe's message of "Wed, 8 Jul 2026 14:36:29 +0000")
Christina Schimpe <christina.schimpe@intel.com> writes:
> Refactor frame.c:inside_main_func to use the new function
> get_main_func_start_pc, which will be called in a following commmit.
> ---
> gdb/frame.c | 37 +++++++++++++++++++++++++------------
> gdb/frame.h | 6 ++++++
> 2 files changed, 31 insertions(+), 12 deletions(-)
>
> diff --git a/gdb/frame.c b/gdb/frame.c
> index cefdde5ed1e..a9f2675ce3a 100644
> --- a/gdb/frame.c
> +++ b/gdb/frame.c
> @@ -2641,27 +2641,26 @@ frame_debug_got_null_frame (const frame_info_ptr &this_frame,
> }
> }
>
> -/* Is this (non-sentinel) frame in the "main"() function? */
> +/* See frame.h. */
>
> -static bool
> -inside_main_func (const frame_info_ptr &this_frame)
> +std::optional<CORE_ADDR>
> +get_main_func_start_pc (gdbarch* gdbarch, const language lang)
The nittest of nits: GDB style is to put the '*' with the variable, not
the type.
Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
> {
> if (current_program_space->symfile_object_file == nullptr)
> - return false;
> + return {};
>
> - CORE_ADDR sym_addr = 0;
> const char *name = main_name ();
> bound_minimal_symbol msymbol
> = lookup_minimal_symbol (current_program_space, name,
> current_program_space->symfile_object_file);
>
> + CORE_ADDR sym_addr = 0;
> if (msymbol.minsym != nullptr)
> sym_addr = msymbol.value_address ();
>
> /* Favor a full symbol in Fortran, for the case where the Fortran main
> is also called "main". */
> - if (msymbol.minsym == nullptr
> - || get_frame_language (this_frame) == language_fortran)
> + if (msymbol.minsym == nullptr || lang == language_fortran)
> {
> /* In some language (for example Fortran) there will be no minimal
> symbol with the name of the main function. In this case we should
--
Thiago
(he/him)
next prev parent reply other threads:[~2026-09-03 6:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 14:36 [PATCH v4 00/13] Add new command to print the shadow stack backtrace Christina Schimpe
2026-07-08 14:36 ` [PATCH v4 01/13] gdb: Generalize handling of the shadow stack pointer Christina Schimpe
2026-07-08 14:36 ` [PATCH v4 02/13] aarch64: Implement gdbarch function top_addr_empty_shadow_stack Christina Schimpe
2026-08-12 22:13 ` Luis
2026-08-25 9:01 ` Joos, Christina
2026-08-29 5:24 ` Thiago Jung Bauermann
2026-08-30 11:14 ` Joos, Christina
2026-09-03 6:49 ` Thiago Jung Bauermann
2026-09-12 6:02 ` Thiago Jung Bauermann
2026-07-08 14:36 ` [PATCH v4 03/13] gdb: Add get_main_func_start_pc to refactor frame.c:inside_main_func Christina Schimpe
2026-09-03 6:53 ` Thiago Jung Bauermann [this message]
2026-07-08 14:36 ` [PATCH v4 04/13] gdb: Refactor 'stack.c:print_frame' Christina Schimpe
2026-07-08 14:36 ` [PATCH v4 05/13] gdb: Introduce 'stack.c:print_pc' function without frame argument Christina Schimpe
2026-07-08 14:36 ` [PATCH v4 06/13] gdb: Refactor 'find_symbol_funname' and 'info_frame_command_core' in stack.c Christina Schimpe
2026-07-08 14:36 ` [PATCH v4 07/13] gdb: Refactor 'stack.c:print_frame_info' Christina Schimpe
2026-07-08 14:36 ` [PATCH v4 08/13] gdb: Add command option 'bt -shadow' to print the shadow stack backtrace Christina Schimpe
2026-09-03 7:37 ` Thiago Jung Bauermann
2026-09-10 19:36 ` Joos, Christina
2026-09-12 5:52 ` Thiago Jung Bauermann
2026-07-08 14:36 ` [PATCH v4 09/13] gdb: Provide gdbarch hook to distinguish shadow stack backtrace elements Christina Schimpe
2026-09-03 7:44 ` Thiago Jung Bauermann
2026-07-08 14:36 ` [PATCH v4 10/13] gdb: Implement the hook 'is_no_return_shadow_stack_address' for amd64 linux Christina Schimpe
2026-09-03 7:49 ` Thiago Jung Bauermann
2026-07-08 14:36 ` [PATCH v4 11/13] gdb: Enable inferior calls in the shadow stack backtrace Christina Schimpe
2026-09-03 7:51 ` Thiago Jung Bauermann
2026-07-08 14:36 ` [PATCH v4 12/13] gdb: Enable signal trampolines " Christina Schimpe
2026-09-03 7:53 ` Thiago Jung Bauermann
2026-07-08 14:36 ` [PATCH v4 13/13] gdb, mi: Add -shadow-stack-list-frames command Christina Schimpe
2026-09-03 8:10 ` Thiago Jung Bauermann
2026-08-04 7:45 ` RE:[PATCH v4 00/13] Add new command to print the shadow stack backtrace Joos, Christina
2026-09-03 6:44 ` [PATCH " Thiago Jung Bauermann
2026-09-10 19:42 ` Joos, Christina
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=87fqzqsu53.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=christina.schimpe@intel.com \
--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