Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Florian Weimer via Gdb <gdb@sourceware.org>
To: "Schimpe, Christina via Gdb" <gdb@sourceware.org>
Cc: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
	 Tom Tromey <tom@tromey.com>,
	 "Schimpe, Christina" <christina.schimpe@intel.com>
Subject: Re: Shadow stack backtrace command name
Date: Fri, 05 Jul 2024 20:16:31 +0200	[thread overview]
Message-ID: <874j93vh4w.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <SN7PR11MB7638463DD955713D5768D3F3F96A2@SN7PR11MB7638.namprd11.prod.outlook.com> (Christina via Gdb Schimpe's message of "Tue, 9 Jan 2024 10:21:02 +0000")

* Christina via Gdb Schimpe:

> However, based on the use cases that I am aware of, I am not sure if
> the user wants to always see the shadow stack bt in the ordinary bt
> output (if shadow stack is enabled).

Based on my experiments, Linux currently does not push the instruction
pointer onto the shadow stack if code is interrupted by a signal.  It
still works because the return mechanism is different.  This would be a
very visible difference between ordinary backtraces and shadow stack
based backtraces.

As far as I understand it, the kernel could change, and it may still be
early enough to make this change.

By the way, is there a way to tell if a process is in shadow stack mode
using upstream GDB today?  Preferably something that does not rely on
glibc internals?

Thanks,
Florian


  reply	other threads:[~2024-07-05 18:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20  9:42 Schimpe, Christina via Gdb
2023-12-20 10:59 ` Guinevere Larsen via Gdb
2023-12-20 15:11   ` Schimpe, Christina via Gdb
2023-12-20 11:38 ` Luis Machado via Gdb
2023-12-20 15:35   ` Schimpe, Christina via Gdb
2023-12-20 15:57     ` Luis Machado via Gdb
2023-12-21  4:35       ` Thiago Jung Bauermann via Gdb
2023-12-21 22:26 ` Shadow stack command to host related subcommands (was Re: Shadow stack backtrace command name) Thiago Jung Bauermann via Gdb
2024-01-09  8:34   ` Schimpe, Christina via Gdb
2023-12-23 18:22 ` Shadow stack backtrace command name Tom Tromey
2023-12-28 22:34   ` Thiago Jung Bauermann via Gdb
2024-01-09 10:21     ` Schimpe, Christina via Gdb
2024-07-05 18:16       ` Florian Weimer via Gdb [this message]
2024-07-09 14:50         ` Schimpe, Christina via Gdb
2024-07-09 15:16           ` Florian Weimer via Gdb
2024-07-10  9:07             ` Schimpe, Christina via Gdb
2024-07-10 10:05               ` Florian Weimer via Gdb
2024-07-10 11:35                 ` Schimpe, Christina via Gdb

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=874j93vh4w.fsf@oldenburg.str.redhat.com \
    --to=gdb@sourceware.org \
    --cc=christina.schimpe@intel.com \
    --cc=fweimer@redhat.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