From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: "Joos, Christina" <christina.joos@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3 02/12] aarch64: Implement gdbarch function top_addr_empty_shadow_stack.
Date: Mon, 03 Aug 2026 18:17:48 +0000 [thread overview]
Message-ID: <877bm72hmb.fsf@linaro.org> (raw)
In-Reply-To: <SN7PR11MB76389EB76E21C87BF4931AA889D52@SN7PR11MB7638.namprd11.prod.outlook.com> (Christina Joos's message of "Mon, 3 Aug 2026 15:17:31 +0000")
Hello Christina,
"Joos, Christina" <christina.joos@intel.com> writes:
> I noticed that I missed to adapt the author of this patch to your name. This was not
> intended. 😊
> I will do that with the next version of this series once I received more feedback
> (together with an update of my last name for the Co-Author).
Not a problem!
Sorry that I wasn't able to review this patch series yet. It's on my
list, but I have fallen behind a bit and trying to catch up. I think
I'll be able to get to it (to v4 actually) this week.
--
Thiago
(he/him)
next prev parent reply other threads:[~2026-08-03 18:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 12:31 [PATCH v3 00/12] Add new command to print the shadow stack backtrace Christina Schimpe
2026-07-06 12:31 ` [PATCH v3 01/12] gdb: Generalize handling of the shadow stack pointer Christina Schimpe
2026-07-06 12:31 ` [PATCH v3 02/12] aarch64: Implement gdbarch function top_addr_empty_shadow_stack Christina Schimpe
2026-08-03 15:17 ` Joos, Christina
2026-08-03 18:17 ` Thiago Jung Bauermann [this message]
2026-08-04 8:02 ` Joos, Christina
2026-07-06 12:31 ` [PATCH v3 03/12] gdb: Add get_main_func_start_pc to refactor frame.c:inside_main_func Christina Schimpe
2026-07-06 12:31 ` [PATCH v3 04/12] gdb: Refactor 'stack.c:print_frame' Christina Schimpe
2026-07-06 12:31 ` [PATCH v3 05/12] gdb: Introduce 'stack.c:print_pc' function without frame argument Christina Schimpe
2026-07-06 12:31 ` [PATCH v3 06/12] gdb: Refactor 'find_symbol_funname' and 'info_frame_command_core' in stack.c Christina Schimpe
2026-07-06 12:31 ` [PATCH v3 07/12] gdb: Refactor 'stack.c:print_frame_info' Christina Schimpe
2026-07-06 12:31 ` [PATCH v3 08/12] gdb: Add command option 'bt -shadow' to print the shadow stack backtrace Christina Schimpe
2026-07-08 9:13 ` Schimpe, Christina
2026-07-06 12:31 ` [PATCH v3 09/12] gdb: Implement the hook 'is_no_return_shadow_stack_address' for amd64 linux Christina Schimpe
2026-07-06 12:31 ` [PATCH v3 10/12] gdb: Enable inferior calls in the shadow stack backtrace Christina Schimpe
2026-07-06 12:31 ` [PATCH v3 11/12] gdb: Enable signal trampolines " Christina Schimpe
2026-07-06 12:31 ` [PATCH v3 12/12] gdb, mi: Add -shadow-stack-list-frames command Christina Schimpe
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=877bm72hmb.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=christina.joos@intel.com \
--cc=gdb-patches@sourceware.org \
/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