http://ghafoorsblog.com/tags/reproduction-case/Recent content in Reproduction-Case on Ghafoor's Personal BlogHugoennoreply@example.com (AG Sayyed)noreply@example.com (AG Sayyed)Copyright © 2024-2026 AG Sayyed. All Rights Reserved.Fri, 15 May 2026 13:20:20 +0100http://ghafoorsblog.com/courses/google/it-automation-content/it-automation-python-pcert/04-troubleshooting-debugging/03-module/003-uderstanding-crash/Thu, 13 Nov 2025 11:06:11 +0000noreply@example.com (AG Sayyed)http://ghafoorsblog.com/courses/google/it-automation-content/it-automation-python-pcert/04-troubleshooting-debugging/03-module/003-uderstanding-crash/<p class="lead text-primary"> This document explains how to investigate application crashes by examining logs, enabling diagnostic logging, tracing system calls, analysing recent changes, and building minimal reproduction cases to isolate root causes. </p> <hr> <h2 id="introduction">Introduction</h2> <p>When an application terminates unexpectedly, the investigation should start with all available evidence and proceed by systematically reducing the problem scope. Logs, tracing tools, and change history provide primary clues.</p> <hr> <h2 id="logs-and-initial-evidence">Logs and Initial Evidence</h2> <p>Logs are the primary source of evidence. Relevant data includes timestamps and error messages around the crash time. Search logs for entries near the known crash time and for messages related to the failing component.</p>