From: Tom Tromey <tom@tromey.com>
To: "Schimpe, Christina via Gdb" <gdb@sourceware.org>
Cc: "Schimpe, Christina" <christina.schimpe@intel.com>
Subject: Re: Shadow stack backtrace command name
Date: Sat, 23 Dec 2023 11:22:39 -0700 [thread overview]
Message-ID: <87a5q0eq34.fsf@tromey.com> (raw)
In-Reply-To: <SN7PR11MB7638DE1337F8F0F0282EBD56F996A@SN7PR11MB7638.namprd11.prod.outlook.com> (Christina via Gdb Schimpe's message of "Wed, 20 Dec 2023 09:42:39 +0000")
>>>>> Schimpe, Christina via Gdb <gdb@sourceware.org> writes:
> A shadow stack is a second stack for a program introduced in the Intel (R)
> Control-Flow Enforcement Technology (CET). The shadow stack is used for
> control transfer operations to store the return addresses.
One question I had is when, as a gdb user, would I want to see this
information?
> It is configurable using "print symbol-filename" and COUNT.
> The command can be called by the following names:
> - "info shadow-stack bt", "info shadow-stack backtrace"
Like others in the thread, I'm -1 on "info" as a prefix.
I liked "bt -shadow", but I was also wondering if the information should
just be integrated into the ordinary backtrace when available... that's
why I'm wondering when I'd want to see this.
Tom
next prev parent reply other threads:[~2023-12-23 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 9:42 Schimpe, Christina
2023-12-20 10:59 ` Guinevere Larsen
2023-12-20 15:11 ` Schimpe, Christina
2023-12-20 11:38 ` Luis Machado
2023-12-20 15:35 ` Schimpe, Christina
2023-12-20 15:57 ` Luis Machado
2023-12-21 4:35 ` Thiago Jung Bauermann
2023-12-21 22:26 ` Shadow stack command to host related subcommands (was Re: Shadow stack backtrace command name) Thiago Jung Bauermann
2024-01-09 8:34 ` Schimpe, Christina
2023-12-23 18:22 ` Tom Tromey [this message]
2023-12-28 22:34 ` Shadow stack backtrace command name Thiago Jung Bauermann
2024-01-09 10:21 ` 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=87a5q0eq34.fsf@tromey.com \
--to=tom@tromey.com \
--cc=christina.schimpe@intel.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).