[Crash-utility] arm64: Fix bt command show wrong stacktrace on ramdump source

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

[Crash-utility] arm64: Fix bt command show wrong stacktrace on ramdump source

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

[Crash-utility] arm64: Fix bt command show wrong stacktrace on ramdump source

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