public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "alahay01 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/26613] New: Arm: Secure stack not supported
Date: Mon, 14 Sep 2020 14:39:05 +0000	[thread overview]
Message-ID: <bug-26613-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=26613

            Bug ID: 26613
           Summary: Arm: Secure stack not supported
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tdep
          Assignee: unassigned at sourceware dot org
          Reporter: alahay01 at gcc dot gnu.org
  Target Milestone: ---

On cortex M, the exception stack can use a secure stack.

This is not currently supported.

See this comment in arm-tdep.c arm_m_exception_cache()

      /* ARMv8-M Exception and interrupt handling is not considered here.
         In the ARMv8-M architecture also EXC_RETURN bit S is controlling if
         the Secure or Non-secure stack was used. To separate Secure and
         Non-secure stacks, processors that are based on the ARMv8-M
         architecture support 4 stack pointers: MSP_S, PSP_S, MSP_NS, PSP_NS.
         In addition, a stack limit feature is provided using stack limit
         registers (accessible using MSR and MRS instructions) in Privileged
         level.  */

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-09-14 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14 14:39 alahay01 at gcc dot gnu.org [this message]
2021-12-13 10:06 ` [Bug tdep/26613] " clyon at gcc dot gnu.org
2022-10-27 23:50 ` luis.machado at arm dot com
2022-10-28  7:36 ` clyon at gcc dot gnu.org

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=bug-26613-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).