Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Joos, Christina" <christina.joos@intel.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"thiago.bauermann@linaro.org" <thiago.bauermann@linaro.org>,
	"tom@tromey.com" <tom@tromey.com>,
	"luis.machado.foss@gmail.com" <luis.machado.foss@gmail.com>
Subject: RE: [PATCH v5 09/13] gdb: Provide gdbarch hook to distinguish shadow stack backtrace elements.
Date: Thu, 24 Sep 2026 13:10:18 +0000	[thread overview]
Message-ID: <SN7PR11MB7638938669AD0BC21E01922E89812@SN7PR11MB7638.namprd11.prod.outlook.com> (raw)
In-Reply-To: <86ik3v9ev0.fsf@gnu.org>

> -----Original Message-----
> From: Eli Zaretskii <eliz@gnu.org>
> Sent: Donnerstag, 24. September 2026 11:30
> To: Joos, Christina <christina.joos@intel.com>
> Cc: gdb-patches@sourceware.org; thiago.bauermann@linaro.org;
> tom@tromey.com; luis.machado.foss@gmail.com
> Subject: Re: [PATCH v5 09/13] gdb: Provide gdbarch hook to distinguish
> shadow stack backtrace elements.
> 
> > From: Christina Joos <christina.joos@intel.com>
> > Cc: thiago.bauermann@linaro.org, tom@tromey.com,
> > luis.machado.foss@gmail.com
> > Date: Thu, 24 Sep 2026 10:33:06 +0200
> >
> > On x86 with CET or on ARM with GCS, there can be elements on the
> > shadow stack which are not return addresses.  In this case, we don't
> > want to print the shadow stack element, but a string instead which
> > describes the frame similar to the normal backtrace command for dummy
> frames or signals.
> >
> > Provide a gdbarch hook to distinguish between return and non-return
> > addresses and to configure a string which is printed instead of the
> > shadow stack element.
> >
> > Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
> > ---
> >  gdb/doc/gdb.texinfo       | 19 +++++++++++++++++++
> >  gdb/gdbarch-gen.c         | 32 ++++++++++++++++++++++++++++++++
> >  gdb/gdbarch-gen.h         | 19 +++++++++++++++++++
> >  gdb/gdbarch_components.py | 25 +++++++++++++++++++++++++
> >  gdb/shadow-stack.c        | 36 +++++++++++++++++++++++++++++++++++-
> >  gdb/shadow-stack.h        | 26 ++++++++++++++++++++++++++
> >  6 files changed, 156 insertions(+), 1 deletion(-)
> 
> AFAIR, I've approved the gdb.texinfo part in v2, right?  And there are no
> changes in that part since then, right?

Hi Eli, 

Thanks a lot for the quick feedback. Yes, you reviewed this patch in v2 already.
And I just double-checked - the gdb.texinfo part did not change for this patch.
I will add your review tag, sorry for missing it.

The gdb.texinfo part did change a bit since v2 for
- "gdb: Add command option 'bt -shadow' to print the shadow stack backtrace"
- "gdb, mi: Add -shadow-stack-list-frames command"

But I saw that you just reviewed the 2 patches again (thanks!).

Christina

________________________________________
Intel Deutschland GmbH 

Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany 

Tel: +49 (89) 99143-0 

www.intel.de 

Managing Directors: Candice Moore, Jeffrey Schneiderman, Ramachandran Sitaraman

Chairperson of the Supervisory Board: Sonja Pierer

Registered Seat: Munich Commercial Register B: Amtsgericht Munich HRB 186928

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

  reply	other threads:[~2026-09-24 13:11 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
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 [this message]
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=SN7PR11MB7638938669AD0BC21E01922E89812@SN7PR11MB7638.namprd11.prod.outlook.com \
    --to=christina.joos@intel.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado.foss@gmail.com \
    --cc=thiago.bauermann@linaro.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