Hi folks,
Sorry for many emails.
I just found out by turning CONFIG_ARM64_PTR_AUTH off in armv8.3 when building
linux, I can avoid this problem.
(I noticed the instruction ‘pacia’ in the function assembly code)
Thank you.
Chan Kim
From: Chan Kim
Sent: Wednesday, April 27, 2022 6:05 PM
Hi, all
I just found that when the linux kernel saves the current x29 and x30 at the
new stack bottom, (it usually does that when entering a function)
The stored x30 value (lr register) has it top 16bits altered to some strange
value. So if I fix those top 16bits to 0x in the stack, and
Hello,
I hope somebody could check this case. It’s easily reproducible for anybody
working with qemu and arm64 linux.
I returned to this problem and made another observation.(showing the back-trace
is really broken).
In another incident of breakpoint at function __driver_attach, (right
Hi, Mulyadi
Thank you for replying.
I found CONFIG_DEBUG_FRAME_POINTER, CONFIG_DEBUG_INFO are already set by
default.
And I tried adding CONFIG_DEBUG_KERNEL, CONFIG_KGDB, CONFIG_GDB_SCRIPTS,
CONFIG_STACKTRACE all to no avail.
Regards,
Chan
From: Mulyadi Santosa
Sent: Friday, April 22,
On Fri, Apr 22, 2022 at 7:30 PM Chan Kim wrote:
> Hello all,
>
> Really strange thing happening here.. I can't see the full stack trace with
> 'bt' command in gdb.
> So I tried with fresh linux-5.10.122 source and qemu-6.2.0 source and it's
> happening too!
> (it's happening when I do
