When using the crash tool to parse the ARM64 dump file with KASAN enabled, I
found that using the bt -a command will cause this tool to crash, the following
is the backtrace infomation.
(gdb) bt
#0 0x5635ac2b166b in arm64_unwind_frame (frame=0x7ffdaf35cb70,
bt=0x7ffdaf35d430)
at arm
Bevis Chen(陳斌_華碩蘇州) 希望回收這封郵件 [arm64: Fix bt command show wrong stacktrace on
ramdump source]。
===
機密資訊 This email and any attachments to it contain confidential informati
Hi all,
I may found a potential bug when using qcom arm64 ramdump to parse backtrace.
Unfortunately, I actually found no processes can use the bt command correctly.
Ex: when start crash tool to do analyse: # crash vmlinux --kaslr=xxx
DDRCS0_0.BIN@0x8000,... --machdep vabits_actual=39
Bevis Chen(陳斌_華碩蘇州) 希望回收這封郵件 [arm64: Fix bt command show wrong stacktrace on
ramdump source]。
===
機密資訊 This email and any attachments to it contain confidential informati
Hi all,
I may found a potential bug when using qcom arm64 ramdump to parse backtrace.
Unfortunately, I actually found no processes can use the bt command correctly.
Ex: when start crash tool to do analyse: # crash vmlinux --kaslr=xxx
DDRCS0_0.BIN@0x8000,... --machdep vabits_actual=39
I think the root cause is CONFIG_DEBUG_INFO_COMPRESSED_ZSTD config is set.
And it requires newer gdb to support the ZSTD decompression.
Not sure if there is any ongoing plan to upgrade gdb or patch it to support
ZSTD ??
Thanks.
--
Crash-utility mailing list -- devel@lists.crash-utility.osci.io
To
Hi bevis_chen,
LGTM, so ack.
Thanks,
Tao Liu
On Thu, Jul 11, 2024 at 2:21 AM wrote:
>
> Hi Tao Liu
> patch has already fixed above.
> thanks for your advice.
> --
> Crash-utility mailing list -- devel@lists.crash-utility.osci.io
> To unsubscribe send an email to devel-le...@lists.crash-utility
Hi Tao Liu
patch has already fixed above.
thanks for your advice.
--
Crash-utility mailing list -- devel@lists.crash-utility.osci.io
To unsubscribe send an email to devel-le...@lists.crash-utility.osci.io
https://${domain_name}/admin/lists/devel.lists.crash-utility.osci.io/
Contribution Guidelines
From dd6b187ac15a237cefe863c4e5b432cf13b9883a Mon Sep 17 00:00:00 2001
From: bevis_chen
Date: Wed, 3 Jul 2024 15:05:44 +0800
Subject: [PATCH] arm64: Fix bt command show wrong stacktrace on ramdump source
If we use crash to parse ramdump(Qcom phone device) rathen than vmcore.
Start command should
