PTRPOSCHAR app store crash report #89
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
BeRo1985/flre#89
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I got a crash report
on samsung r9q (Galaxy S21 FE 5G) with Android 14 (SDK 34)
If I put the address in gdb, it gives
Perhaps something is wrong with CurrentChunk
Thank you for the bug report. However, it appears there's a misunderstanding in the approach taken to diagnose the crash report. The disassembled code provided is based on the x86 architecture, which is not fully applicable to the crash context in this case. The crash occurred on a Samsung Galaxy S21 FE 5G device running Android 14 (SDK 34), which uses the ARM architecture, specifically AArch64 for 64-bit ARM processors.
To accurately diagnose the issue, one would need to analyze the crash using an AArch64 disassembler or debugger, as the x86 code and addresses will not correspond to the actual execution path or memory layout on the device where the crash was reported. Adjusting the analysis to focus on the correct architecture is essential for identifying the root cause of the SIGSEGV (Segmentation Fault).
In summary, to move forward with debugging, ensure that the analysis is performed with the correct architecture in mind, focusing on AArch64 rather than x86. This involves doing an analysis directly on the AArch64
liblclapp.sofrom the[whatever-stripped-away]arm64_v8a.apkfile, which, in the end, is just a ZIP file with a different file extension. This approach will provide more accurate insights into the crash's root cause by examining the correct instruction set and memory addresses relevant to the device and application in question.But, however, I'll take a look into it regarding with a prospect towards CurrentChunk.
Here is the correct disassembler (but it is the same file, you can see they both start with a9bf7bfd with reveerse endian)