# debugging

Learning how programs die, detective-style. This is Part 1 of a three-part series: first, understand the anatomy — CPU, stack, return addresses, segfault — before you can investigate the crime scene and catch the killer. A quiz at every floor. Pass to proceed.

Autopsy trilogy, Part 2. Enter the core dump crime scene, learn the red zone and signal handler roles, then move from coroner to epidemiologist: use a year of citywide death records to solve the first bug, a poisoned well called a bad host.

The autopsy trilogy finale. The remaining 'return-to-null' murders all died during C++ exception unwinding — a teleport, not a normal return. The killer: an 18-year-old race in GNU libunwind, with a murder window one instruction wide (~100 picoseconds). Plus Fermi estimation to check the math.

Indie hacker Ramya's OpenClaw agent kept losing its memory. She spent 5 days debugging — from compaction amnesia, garbage search results, retrieval not triggering, long session context loss, to a system prompt that bloated by 28%. Here are her 10 hard-won lessons.