public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ctice42 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/27987] aarch64 prologue unwinder does not correctly handle -fpatchable-function-entry=2 flag
Date: Sat, 26 Jun 2021 06:28:25 +0000 [thread overview]
Message-ID: <bug-27987-4717-94fcJ9YQP3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27987-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27987
--- Comment #2 from ctice42 at gmail dot com ---
Here is the disassembly of the first few instructions for the first four
functions on the stack:
Dump of assembler code for function kgdb_breakpoint:
0xffff800010323a50 <+0>: bti c
0xffff800010323a54 <+4>: mov x9, x30
0xffff800010323a58 <+8>: nop
0xffff800010323a5c <+12>: paciasp
0xffff800010323a60 <+16>: stp x29, x30, [sp, #-16]!
0xffff800010323a64 <+20>: mov x29, sp
+++++++++++++++++++++++++++++++++++++++
Dump of assembler code for function sysrq_handle_dbg:
0xffff80001032404c <+0>: bti c
0xffff800010324050 <+4>: mov x9, x30
0xffff800010324054 <+8>: nop
0xffff800010324058 <+12>: paciasp
0xffff80001032405c <+16>: stp x29, x30, [sp, #-16]!
0xffff800010324060 <+20>: mov x29, sp
+++++++++++++++++++++++++++++++++++++++
Dump of assembler code for function __handle_sysrq:
0xffff8000111ef174 <+0>: bti c
0xffff8000111ef178 <+4>: mov x9, x30
0xffff8000111ef17c <+8>: nop
0xffff8000111ef180 <+12>: paciasp
0xffff8000111ef184 <+16>: sub sp, sp, #0x70
0xffff8000111ef188 <+20>: stp x29, x30, [sp, #16]
+++++++++++++++++++++++++++++++++++++++
Dump of assembler code for function __handle_sysrq:
0xffff8000111ef174 <+0>: bti c
0xffff8000111ef178 <+4>: mov x9, x30
0xffff8000111ef17c <+8>: nop
0xffff8000111ef180 <+12>: paciasp
0xffff8000111ef184 <+16>: sub sp, sp, #0x70
0xffff8000111ef188 <+20>: stp x29, x30, [sp, #16]
Please let me know if you need more.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-06-26 6:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 15:39 [Bug backtrace/27987] New: " ctice42 at gmail dot com
2021-06-16 15:44 ` [Bug backtrace/27987] " ctice42 at gmail dot com
2021-06-25 13:01 ` luis.machado at linaro dot org
2021-06-26 6:28 ` ctice42 at gmail dot com [this message]
2021-06-28 17:52 ` luis.machado at linaro dot org
2021-06-29 14:00 ` luis.machado at linaro dot org
2021-06-29 14:34 ` luis.machado at linaro dot org
2021-06-29 17:07 ` luis.machado at linaro dot org
2021-06-29 17:08 ` luis.machado at linaro dot 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-27987-4717-94fcJ9YQP3@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).