0 views collected around this technical thread.
This article introduces the art‑parser tool for offline Android core‑dump analysis, detailing its origin, project structure, core‑file acquisition methods, page‑repair techniques, object inspection commands, and the challenges of open‑sourcing the utility for mobile developers.
This article explains how Android native developers can capture and recover from controllable SIGSEGV crashes by registering signal handlers and using sigsetjmp/siglongjmp to emulate a try‑catch mechanism, complete with sample JNI code and practical considerations.
This article provides an in‑depth guide to analyzing Android native crashes, explaining common SIGSEGV types, interpreting tombstone logs, extracting register and memory information, using coredumps, and employing tools such as GDB, lldb, ASAN, HWASAN, and assembly inspection to trace and resolve crash causes.
The article explains Android native crashes (NE) by describing .so file composition, the need for un‑stripped libraries, how to view and generate stripped/un‑stripped binaries, and detailed workflows using ndk‑stack, DropBox, BreakPad, objdump, addr2line, and minidump_stackwalk to reconstruct stack traces and pinpoint source lines.
An in‑depth analysis of a long‑standing native crash on Android caused by thread‑unsafe initialization of GURL during CookieManager.getCookie calls, detailing stack traces, investigation steps, source code examination, and a lightweight application‑level synchronization fix that eliminated the issue in production.