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: Sat, 29 Oct 2022 10:47:28 +0000	[thread overview]
Message-ID: <bug-29716-4717-j17FM1JJ6i@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 #1 from tomas.vanek at fbl dot cz ---
Another problem in unwinding of interstate returns:

A secure procedure with cmse_nonsecure_entry attribute is compiled with
an epilogue ending by
 bxns lr

When a non-secure context called such procedure, the stack unwinder (usually
dwarf2 unwinder) does not know about cmse_nonsecure_entry attribute, does not
see 'bxns' at the return and therefore assumes normal return keeping security
state unchanged. This causes incorrect unwinding of following frames as the
secure stack is used instead of insecure.

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

  reply	other threads:[~2022-10-29 10:47 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 ` tomas.vanek at fbl dot cz [this message]
2022-10-29 15:43 ` [Bug tdep/29716] " 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
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-j17FM1JJ6i@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).