Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Joos, Christina" <christina.joos@intel.com>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "tom@tromey.com" <tom@tromey.com>,
	"luis.machado.foss@gmail.com" <luis.machado.foss@gmail.com>,
	Eli Zaretskii <eliz@gnu.org>
Subject: RE: [PING^2][PATCH v5 00/13] Add new command to print the shadow stack backtrace
Date: Thu, 15 Oct 2026 19:33:11 +0000	[thread overview]
Message-ID: <SN7PR11MB7638918BAB1C46ABB6772D90899C2@SN7PR11MB7638.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87cxta96hg.fsf@linaro.org>

> -----Original Message-----
> From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
> Sent: Donnerstag, 15. Oktober 2026 20:14
> To: Joos, Christina <christina.joos@intel.com>
> Cc: gdb-patches@sourceware.org; tom@tromey.com;
> luis.machado.foss@gmail.com
> Subject: Re: [PING][PATCH v5 00/13] Add new command to print the shadow
> stack backtrace
> 
> "Joos, Christina" <christina.joos@intel.com> writes:
> 
> >> -----Original Message-----
> >> From: Christina Joos <christina.joos@intel.com>
> >> Sent: Donnerstag, 24. September 2026 10:33
> >> To: gdb-patches@sourceware.org
> >> Cc: thiago.bauermann@linaro.org; tom@tromey.com;
> >> luis.machado.foss@gmail.com
> >> Subject: [PATCH v5 00/13] Add new command to print the shadow stack
> >> backtrace
> >>
> >> Hi all,
> >>
> >> this is v5 of the series
> >> "Add new command to print the shadow stack backtrace".
> >>
> >> This version addresses the feedback from Luis and Thiago.
> >> Some parts of this series are already approved, but for some patches
> >> I still need approval from the global maintainers before I can merge this.
> >
> > Kindly pinging for feedback!
> 
> Just to be explicit about it, from my side the patch series looks good.

Thanks a lot for your reviews and approvals!

> It does need review/approval for the generic code.

I was just about to ping on this one more time, so ... kindly pinging for feedback!😊

This is an overview about the current review state; those patches still need approval (generic code):

01: gdb: Generalize handling of the shadow stack pointer
=> Approved for the aarch64 parts but still needs an approval for the generic code.
03: gdb: Add get_main_func_start_pc to refactor frame.c:inside_main_func.
08: gdb: Add command option 'bt -shadow' to print the shadow stack backtrace.
09: gdb: Provide gdbarch hook to distinguish shadow stack backtrace elements.  
11: gdb: Enable inferior calls in the shadow stack backtrace.
12: gdb: Enable signal trampolines in the shadow stack backtrace.
13: gdb, mi: Add -shadow-stack-list-frames command

Already approved by Tom or Thiago:
02: aarch64: Implement gdbarch function top_addr_empty_shadow_stack.
04: gdb: Refactor 'stack.c:print_frame'.
05: gdb: Introduce 'stack.c:print_pc' function without frame argument.
06: gdb: Refactor 'find_symbol_funname' and 'info_frame_command_core' in stack.c.
07: gdb: Refactor 'stack.c:print_frame_info'.

This one I may self-approve, but any feedback/reviews are more than welcome:
10: gdb: Implement the hook 'is_no_return_shadow_stack_address' for amd64 linux.  

The docs part is Reviewed-By Eli.

Kind Regards,
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-10-15 19:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24  8:32 [PATCH " 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
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
2026-10-08  7:46 ` [PING][PATCH v5 00/13] Add new command to print the shadow stack backtrace Joos, Christina
2026-10-15 18:14   ` Thiago Jung Bauermann
2026-10-15 19:33     ` Joos, Christina [this message]

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=SN7PR11MB7638918BAB1C46ABB6772D90899C2@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