From: "Schimpe, Christina" <christina.schimpe@intel.com>
To: "Schimpe, Christina" <christina.schimpe@intel.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"Thiago Jung Bauermann" <thiago.bauermann@linaro.org>
Subject: RE: [PATCH 0/9] Add new command to print the shadow stack backtrace
Date: Thu, 25 Sep 2025 11:46:00 +0000 [thread overview]
Message-ID: <SN7PR11MB763886927AD49BA942D79324F91FA@SN7PR11MB7638.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20250923111842.4091694-1-christina.schimpe@intel.com>
Hi Thiago,
I did not test the "bt shadow" command for ARM's GCS. Does the command make sense for GCS, too ?
If yes, does the implementation I shared here makes sense to you in general?
I tried to address the different Aarch and Intel behavior we discussed here
https://sourceware.org/pipermail/gdb-patches/2025-June/218947.html
by introducing a new gdbarch hook top_addr_empty_shadow_stack.
Does that go into the right direction for your purposes?
Thanks,
Christina
> -----Original Message-----
> From: Christina Schimpe <christina.schimpe@intel.com>
> Sent: Tuesday, September 23, 2025 1:19 PM
> To: gdb-patches@sourceware.org
> Subject: [PATCH 0/9] Add new command to print the shadow stack backtrace
>
> Hi all,
>
> as already indicated in the discussion
> https://sourceware.org/pipermail/gdb/2023-December/051024.html
> I'd like to add a command to print the shadow stack backtrace.
>
> In the discussion above the main conclusion was to use the ordinary backtrace
> command with a new flag: "bt -shadow".
> I chose a similar direction, but decided against the flag "-shadow"
> in favor of a new subcommand of the ordinary backtrace command:
> "bt shadow".
>
> This is an example shadow stack backtrace on amd64:
> ~~~
> (gdb) bt shadow
> #0 0x000000000040111f in call1 at amd64-shadow-stack.c:14
> #1 0x000000000040112f in main at amd64-shadow-stack.c:21
> #2 0x00007ffff7c3fe70 in __libc_start_call_main at
> ../sysdeps/nptl/libc_start_call_main.h:58
> #3 0x00007ffff7c3ff20 in __libc_start_main_impl at ../csu/libc-start.c:128
> #4 0x0000000000401045 in _start
> ~~~
>
> I am happy about your feedback!
>
> Christina
>
>
> Christina Schimpe (9):
> gdb: Generalize handling of the shadow stack pointer.
> gdb: Refactor 'stack.c:print_frame'.
> gdb: Introduce 'stack.c:print_pc' function without frame argument.
> gdb: Refactor 'find_symbol_funname' and 'info_frame_command_core' in
> stack.c.
> gdb: Refactor 'stack.c:print_frame_info'.
> gdb: Implement 'bt shadow' to print the shadow stack backtrace.
> gdb: Provide gdbarch hook to distinguish shadow stack backtrace
> elements.
> gdb: Implement the hook 'is_no_return_shadow_stack_address' for amd64
> linux.
> gdb, mi: Add -shadow-stack-list-frames command
>
> gdb/Makefile.in | 2 +
> gdb/NEWS | 17 +
> gdb/aarch64-linux-tdep.c | 51 +-
> gdb/aarch64-tdep.c | 42 +-
> gdb/amd64-linux-tdep.c | 164 ++---
> gdb/amd64-tdep.c | 20 +
> gdb/annotate.c | 93 ++-
> gdb/annotate.h | 18 +-
> gdb/doc/gdb.texinfo | 114 +++
> gdb/gdbarch-gen.c | 158 ++++-
> gdb/gdbarch-gen.h | 80 ++-
> gdb/gdbarch.h | 1 +
> gdb/gdbarch_components.py | 100 ++-
> gdb/infcall.c | 4 +-
> gdb/linux-tdep.c | 2 +
> gdb/mi/mi-cmd-stack.c | 146 ++++
> gdb/mi/mi-cmds.c | 2 +
> gdb/mi/mi-cmds.h | 1 +
> gdb/shadow-stack.c | 662 ++++++++++++++++++
> gdb/shadow-stack.h | 106 +++
> gdb/stack.c | 382 ++++++----
> gdb/stack.h | 55 ++
> .../amd64-shadow-stack-backtrace-signal.exp | 54 ++
> .../gdb.arch/amd64-shadow-stack-cmds.exp | 88 +++
> .../gdb.arch/amd64-shadow-stack-signal.c | 31 +
> gdb/testsuite/gdb.base/help.exp | 6 +-
> gdb/testsuite/gdb.base/options.exp | 7 +-
> .../gdb.mi/mi-shadow-stack-signal.exp | 69 ++
> gdb/testsuite/gdb.mi/mi-shadow-stack.exp | 65 ++
> 29 files changed, 2105 insertions(+), 435 deletions(-) create mode 100644
> gdb/shadow-stack.c create mode 100644 gdb/shadow-stack.h create mode
> 100644 gdb/testsuite/gdb.arch/amd64-shadow-stack-backtrace-signal.exp
> create mode 100644 gdb/testsuite/gdb.arch/amd64-shadow-stack-signal.c
> create mode 100644 gdb/testsuite/gdb.mi/mi-shadow-stack-signal.exp
> create mode 100644 gdb/testsuite/gdb.mi/mi-shadow-stack.exp
>
> --
> 2.34.1
>
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de
> Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
> Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2025-09-25 11:46 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 11:18 Christina Schimpe
2025-09-23 11:18 ` [PATCH 1/9] gdb: Generalize handling of the shadow stack pointer Christina Schimpe
2025-10-31 1:31 ` Thiago Jung Bauermann
2025-11-17 11:18 ` Schimpe, Christina
2025-11-26 4:19 ` Thiago Jung Bauermann
2025-12-30 10:39 ` Schimpe, Christina
2025-09-23 11:18 ` [PATCH 2/9] gdb: Refactor 'stack.c:print_frame' Christina Schimpe
2025-10-03 20:05 ` Tom Tromey
2025-09-23 11:18 ` [PATCH 3/9] gdb: Introduce 'stack.c:print_pc' function without frame argument Christina Schimpe
2025-10-03 19:56 ` Tom Tromey
2025-09-23 11:18 ` [PATCH 4/9] gdb: Refactor 'find_symbol_funname' and 'info_frame_command_core' in stack.c Christina Schimpe
2025-10-03 19:55 ` Tom Tromey
2025-09-23 11:18 ` [PATCH 5/9] gdb: Refactor 'stack.c:print_frame_info' Christina Schimpe
2025-10-03 20:03 ` Tom Tromey
2025-09-23 11:18 ` [PATCH 6/9] gdb: Implement 'bt shadow' to print the shadow stack backtrace Christina Schimpe
2025-09-23 11:47 ` Eli Zaretskii
2025-09-25 11:06 ` Schimpe, Christina
2025-09-25 13:19 ` Eli Zaretskii
2025-09-25 14:58 ` Simon Marchi
2025-09-26 7:45 ` Schimpe, Christina
2025-10-29 15:05 ` Schimpe, Christina
2025-10-29 15:28 ` Guinevere Larsen
2025-11-03 19:47 ` Schimpe, Christina
2025-11-04 11:53 ` Guinevere Larsen
2025-11-05 16:33 ` Schimpe, Christina
2025-10-13 1:17 ` Thiago Jung Bauermann
2025-10-13 7:19 ` Schimpe, Christina
2025-10-31 4:39 ` Thiago Jung Bauermann
2025-11-06 14:23 ` Schimpe, Christina
2025-10-03 20:15 ` Tom Tromey
2025-10-12 19:45 ` Schimpe, Christina
2026-02-19 17:24 ` Tom Tromey
2026-03-02 12:24 ` Schimpe, Christina
2025-10-31 4:02 ` Thiago Jung Bauermann
2025-11-17 20:14 ` Schimpe, Christina
2025-11-26 4:07 ` Thiago Jung Bauermann
2025-11-26 16:29 ` Thiago Jung Bauermann
2026-01-22 17:04 ` Schimpe, Christina
2026-03-06 2:35 ` Thiago Jung Bauermann
2026-01-15 14:05 ` Schimpe, Christina
2025-09-23 11:18 ` [PATCH 7/9] gdb: Provide gdbarch hook to distinguish shadow stack backtrace elements Christina Schimpe
2025-09-23 11:49 ` Eli Zaretskii
2025-09-25 11:10 ` Schimpe, Christina
2025-11-02 21:20 ` Thiago Jung Bauermann
2025-11-12 17:28 ` Schimpe, Christina
2025-11-16 18:39 ` Thiago Jung Bauermann
2025-11-17 11:51 ` Schimpe, Christina
2025-09-23 11:18 ` [PATCH 8/9] gdb: Implement the hook 'is_no_return_shadow_stack_address' for amd64 linux Christina Schimpe
2025-11-26 4:22 ` Thiago Jung Bauermann
2025-09-23 11:18 ` [PATCH 9/9] gdb, mi: Add -shadow-stack-list-frames command Christina Schimpe
2025-09-23 11:53 ` Eli Zaretskii
2025-09-25 11:32 ` Schimpe, Christina
2025-10-03 20:17 ` Tom Tromey
2025-10-12 19:54 ` Schimpe, Christina
2025-10-13 0:06 ` Thiago Jung Bauermann
2025-11-26 4:26 ` Thiago Jung Bauermann
2026-01-22 17:01 ` Schimpe, Christina
2026-03-06 2:44 ` Thiago Jung Bauermann
2025-09-25 11:46 ` Schimpe, Christina [this message]
2025-10-08 1:46 ` [PATCH 0/9] Add new command to print the shadow stack backtrace Thiago Jung Bauermann
2025-10-13 1:18 ` Thiago Jung Bauermann
2025-10-13 6:34 ` Schimpe, Christina
2025-10-29 14:52 ` Schimpe, Christina
2025-10-31 0:47 ` Thiago Jung Bauermann
2025-12-30 10:16 ` Schimpe, Christina
2026-03-06 2:30 ` Thiago Jung Bauermann
2026-03-12 9:53 ` Schimpe, 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=SN7PR11MB763886927AD49BA942D79324F91FA@SN7PR11MB7638.namprd11.prod.outlook.com \
--to=christina.schimpe@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@linaro.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