This article explains why Linux programs may exit unexpectedly, introduces the backtrace utility and its underlying call‑stack mechanism, and provides step‑by‑step instructions—including compilation flags, signal handling, and address‑to‑source mapping—to accurately locate the root cause of crashes.
This article explains common causes of unexpected Linux program termination and demonstrates how to employ the backtrace utility, along with signal handling and related functions, to capture and analyze stack traces, enabling precise identification and resolution of issues such as memory overflows, null pointer dereferences, and other runtime errors.
The article explains why backtracing with eBPF fentry on arm64 is harder than on x86, details the stack layout differences, shows how recent commits changed register saving, and provides a practical detection routine to locate the frame pointer and retrieve the tracee's instruction pointer.
This article explains Rust's panic! macro, covering how to invoke it, its default behavior, options for stack unwinding versus aborting, practical code examples, and how to use backtraces for debugging, while advising when to prefer Result for recoverable errors.
Baidu’s iOS solution monitors single memory allocations exceeding an 8 MB threshold by intercepting malloc_logger and capturing stack traces with backtrace, merging online user‑scenario data and offline pipelines to identify large‑allocation hotspots, reduce OOM crashes, and give developers actionable debugging insight.
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 the Matrix team created a low‑overhead iOS/macOS energy‑consumption monitor that captures high‑CPU thread stacks, builds aggregated power‑consume stacks, and helps pinpoint heating scenarios such as image uploads, VoIP calls, and game usage.
