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 how Android’s debuggerd daemon registers signal handlers, captures crashes, generates detailed tombstone files containing process, thread, register and memory information, and provides a step‑by‑step method for analyzing these files with tools like addr2line and objdump to locate the fault.
This article explains how Android native exceptions (NE) are captured, processed, and logged as tombstone files, detailing the signal registration, debuggerd workflow, crash_dump execution, unwinder backtrace generation, and how developers can analyze the resulting data using tools like addr2line.
This article details Ctrip's practical design and implementation of a bidirectional Redis synchronization system across data centers, covering replication loop breaking, conflict resolution with Last Write Wins and Vector Clocks, tombstone handling, garbage collection strategies, and expiration policies to ensure data consistency.
