Tagged articles
8 articles
Page 1 of 1
Alibaba Cloud Observability
Alibaba Cloud Observability
Oct 27, 2025 · Mobile Development

Mastering HarmonyOS Crash Monitoring: From Native Crashes to ArkTS Stack Traces

Learn how to monitor and analyze crashes in HarmonyOS Next by handling native C/C++ signals and ArkTS/JavaScript errors, using hiAppEvent watchers, simulating crash scenarios, and leveraging build artifacts such as source maps, debug .so files, and nameCache for precise stack trace reconstruction and improved app stability.

HarmonyOSNative CrasharkTS
0 likes · 17 min read
Mastering HarmonyOS Crash Monitoring: From Native Crashes to ArkTS Stack Traces
Sohu Tech Products
Sohu Tech Products
Jul 20, 2022 · Mobile Development

Understanding and Debugging Native Crashes on Android: Tombstone and Coredump Analysis

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.

AndroidAssemblyMemory analysis
0 likes · 39 min read
Understanding and Debugging Native Crashes on Android: Tombstone and Coredump Analysis
vivo Internet Technology
vivo Internet Technology
Feb 22, 2021 · Mobile Development

Understanding and Analyzing Native Crashes (NE) in Android Development

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.

AndroidBreakpadNDK
0 likes · 18 min read
Understanding and Analyzing Native Crashes (NE) in Android Development
OPPO Kernel Craftsman
OPPO Kernel Craftsman
Jul 31, 2020 · Mobile Development

Decoding Android Native Crashes: From Signal Handling to Tombstone Analysis

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.

AndroidMobile DevelopmentNative Crash
0 likes · 11 min read
Decoding Android Native Crashes: From Signal Handling to Tombstone Analysis
Watermelon Video Tech Team
Watermelon Video Tech Team
Apr 7, 2020 · Mobile Development

Investigation and Fix of Android Native Crash in CookieManager.getCookie Caused by Thread‑Unsafe GURL Initialization

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.

AndroidCookieManagerGURL
0 likes · 10 min read
Investigation and Fix of Android Native Crash in CookieManager.getCookie Caused by Thread‑Unsafe GURL Initialization