public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tomas.vanek at fbl dot cz" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/29716] Arm v8 M-profile FNC_RETURN unwinder uses wrong stack
Date: Fri, 04 Nov 2022 18:24:15 +0000	[thread overview]
Message-ID: <bug-29716-4717-UjzWYPry9V@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29716-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from tomas.vanek at fbl dot cz ---
My modifications to ST GTZC_TZSC_MPCBB_TrustZone example to exercise FNC_RETURN
and return from secure to non-secure (LED3 indicates secure mode):

Secure/main.c:
  void SECURE_Mode(funcptr back_ns);
  void NSCalledFromSec(void);
  void NSCalledFromNS(void);
  void SecCalledFromNS(void);

  static void SecCalledFromSec(funcptr back_ns)
  {
        if (back_ns) {
                back_ns();
        }
  }

  CMSE_NS_ENTRY void SECURE_Mode(funcptr back_ns)
  {
        HAL_GPIO_WritePin(LED3_GPIO_Port, LED3_Pin, 1);

        SecCalledFromSec(back_ns);
  }

  CMSE_NS_ENTRY void SecCalledFromNS(void)
  {
        HAL_GPIO_WritePin(LED3_GPIO_Port, LED3_Pin, 1);
  }

NonSecure/main.c:

  void NSCalledFromNS(void)
  {
        SecCalledFromNS();
        HAL_GPIO_WritePin(LED3_GPIO_Port, LED3_Pin, 0);
  }

  void NSCalledFromSec(void)
  {
        HAL_GPIO_WritePin(LED3_GPIO_Port, LED3_Pin, 0);
        NSCalledFromNS();
  }

  int main(void)
  {
...
add to while loop:
        SECURE_Mode(&NSCalledFromSec);
        HAL_GPIO_WritePin(LED3_GPIO_Port, LED3_Pin, 0);

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

  parent reply	other threads:[~2022-11-04 18:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 20:59 [Bug tdep/29716] New: " tomas.vanek at fbl dot cz
2022-10-29 10:47 ` [Bug tdep/29716] " tomas.vanek at fbl dot cz
2022-10-29 15:43 ` tomas.vanek at fbl dot cz
2022-11-04 15:36 ` torbjorn.svensson at st dot com
2022-11-04 18:01 ` tomas.vanek at fbl dot cz
2022-11-04 18:24 ` tomas.vanek at fbl dot cz [this message]
2022-11-04 20:54 ` tomas.vanek at fbl dot cz
2022-11-05  9:50 ` tomas.vanek at fbl dot cz

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-29716-4717-UjzWYPry9V@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).