From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Christina Joos <christina.joos@intel.com>
Cc: gdb-patches@sourceware.org, tom@tromey.com,
luis.machado.foss@gmail.com
Subject: Re: [PATCH v5 02/13] aarch64: Implement gdbarch function top_addr_empty_shadow_stack.
Date: Thu, 24 Sep 2026 21:04:18 +0000 [thread overview]
Message-ID: <87h5jel5t9.fsf@linaro.org> (raw)
In-Reply-To: <20260924083311.1961530-3-christina.joos@intel.com>
Christina Joos <christina.joos@intel.com> writes:
> From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
>
> With the implementation of that gdbarch function we can remove
> the arch specific function aarch64_linux_dwarf2_prev_gcspr and
> use the generalized function dwarf2_prev_ssp instead.
>
> Co-Authored-By: Christina Joos <christina.joos@intel.com>
> ---
> gdb/aarch64-linux-tdep.c | 51 ++--------------------------------------
> gdb/aarch64-tdep.c | 31 ++++++++++++++++++++++--
> 2 files changed, 31 insertions(+), 51 deletions(-)
I guess I don't need to approve this one. :)
Though for the avoidance of doubt, it is.
--
Thiago
(he/him)
next prev parent reply other threads:[~2026-09-24 21:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 8:32 [PATCH v5 00/13] Add new command to print the shadow stack backtrace Christina Joos
2026-09-24 8:32 ` [PATCH v5 01/13] gdb: Generalize handling of the shadow stack pointer Christina Joos
2026-09-24 21:03 ` Thiago Jung Bauermann
2026-09-24 8:32 ` [PATCH v5 02/13] aarch64: Implement gdbarch function top_addr_empty_shadow_stack Christina Joos
2026-09-24 21:04 ` Thiago Jung Bauermann [this message]
2026-09-24 8:33 ` [PATCH v5 03/13] gdb: Add get_main_func_start_pc to refactor frame.c:inside_main_func Christina Joos
2026-09-24 8:33 ` [PATCH v5 04/13] gdb: Refactor 'stack.c:print_frame' Christina Joos
2026-09-24 8:33 ` [PATCH v5 05/13] gdb: Introduce 'stack.c:print_pc' function without frame argument Christina Joos
2026-09-24 8:33 ` [PATCH v5 06/13] gdb: Refactor 'find_symbol_funname' and 'info_frame_command_core' in stack.c Christina Joos
2026-09-24 8:33 ` [PATCH v5 07/13] gdb: Refactor 'stack.c:print_frame_info' Christina Joos
2026-09-24 8:33 ` [PATCH v5 08/13] gdb: Add command option 'bt -shadow' to print the shadow stack backtrace Christina Joos
2026-09-24 9:37 ` Eli Zaretskii
2026-09-24 8:33 ` [PATCH v5 09/13] gdb: Provide gdbarch hook to distinguish shadow stack backtrace elements Christina Joos
2026-09-24 9:29 ` Eli Zaretskii
2026-09-24 13:10 ` Joos, Christina
2026-09-24 8:33 ` [PATCH v5 10/13] gdb: Implement the hook 'is_no_return_shadow_stack_address' for amd64 linux Christina Joos
2026-09-24 8:33 ` [PATCH v5 11/13] gdb: Enable inferior calls in the shadow stack backtrace Christina Joos
2026-09-24 8:33 ` [PATCH v5 12/13] gdb: Enable signal trampolines " Christina Joos
2026-09-24 8:33 ` [PATCH v5 13/13] gdb, mi: Add -shadow-stack-list-frames command Christina Joos
2026-09-24 9:39 ` Eli Zaretskii
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=87h5jel5t9.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=christina.joos@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado.foss@gmail.com \
--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