0Pricing
Production Debugging & Incident Response Playbook · Aula

Depuração posterior com despejos de memória

Aprenda a analisar despejos de memória e relatórios de falhas para depurar problemas ocorridos no passado, sem acesso ao sistema ativo.

Depuração posterior com despejos de memória é uma aula grátis de Production Debugging & Incident Response Playbook no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Production Debugging & Incident Response Playbook, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Production Debugging & Incident Response Playbook inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Debugging After the Fact

Welcome! In this lesson, we'll explore post-mortem debugging. This powerful technique lets you investigate software failures after they've occurred, without needing to reproduce the issue live.

It's incredibly useful when you can't attach a debugger directly to a crashing application, especially in production environments.

What's a Core Dump?

The cornerstone of post-mortem debugging is the core dump. Think of it as a snapshot of a program's entire memory space and CPU state at the exact moment it crashed.

  • It's a file generated by the operating system.
  • It contains critical information about the program's execution.
  • It helps you understand why a crash happened.

When Do Core Dumps Happen?

Core dumps are typically generated when a program encounters a severe, unhandled error that causes it to terminate unexpectedly. Common scenarios include:

  • Segmentation Faults (Segfaults): Accessing invalid memory.
  • Unhandled Exceptions: Language-specific errors not caught by the program.
  • Assertion Failures: When a program's internal assumptions are violated.
  • Program Crashes: Any abrupt, abnormal termination.

Enabling Core Dumps (Linux)

On Linux systems, core dump generation might be disabled by default or limited in size. You can enable it:

  • Temporarily: Use ulimit -c unlimited in your shell session.
  • System-wide: Modify /etc/sysctl.conf (e.g., kernel.core_pattern to specify output path and filename format).

Without proper configuration, your system might not save core dumps when crashes occur.

Core Dump Contents

A core dump is packed with forensic data. It typically includes:

  • Memory Image: A copy of the program's entire virtual memory.
  • CPU Register Values: The state of the CPU registers at the crash time.
  • Stack Trace: The sequence of function calls leading up to the crash.
  • Process Information: Process ID, signal that caused the crash, executable path.
  • Loaded Libraries: Information about shared libraries linked to the program.

Key Analysis Tools

To make sense of a core dump, you need specialized tools. Some popular ones include:

  • GDB (GNU Debugger): Widely used for C/C++ programs on Linux/Unix.
  • WinDbg: Microsoft's powerful debugger for Windows applications.
  • jstack/jmap: For Java applications, these tools can extract thread dumps and memory maps that act as a form of 'core dump'.
  • Delve: A debugger for Go programs.

We'll focus on GDB as a common example.

Crash Program Demo

Let's look at a simple C program that will intentionally cause a segmentation fault. This will generate a core dump file if your system is configured to do so.

Try compiling and running this code:

#include <stdio.h>
#include <stdlib.h>

int main() {
  int *ptr = NULL; // Declare a null pointer
  printf("Attempting to dereference a null pointer...\n");
  *ptr = 10;       // This line will cause a segmentation fault
  printf("This line will not be reached.\n");
  return 0;
}

Basic GDB Usage: Backtrace

After the program crashes and creates a core dump (e.g., core or core.PID), you can load it into GDB. Assuming your executable is a.out:

gdb ./a.out core
bt

The bt (backtrace) command is essential. It shows the call stack leading to the crash, helping you pinpoint the exact function and line number where the error occurred.

Inspecting Variables with GDB

Once you have the backtrace, you can navigate the stack frames (e.g., using frame N where N is the frame number). Then, you can inspect variable values at that point in time:

  • print variable_name: Shows the value of a specific variable.
  • info locals: Lists all local variables in the current stack frame and their values.

This helps you understand the state of the program's data when it crashed.

Core Dump Quiz

Let's check your understanding of core dumps.

Recap: Post-mortem Power

Great work! You've learned about the power of post-mortem debugging using core dumps.

  • Core dumps are memory snapshots of crashed programs.
  • They contain vital info like stack traces and variable states.
  • Tools like GDB help analyze them without live access.

This technique is indispensable for debugging hard-to-reproduce or production-only issues, enabling you to fix problems even after the event.

Perguntas Frequentes

A aula “Depuração posterior com despejos de memória” é grátis?

Sim — o texto completo de “Depuração posterior com despejos de memória” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Production Debugging & Incident Response Playbook, atualize para CoddyKit PRO. O curso de Production Debugging & Incident Response Playbook inclui 4 aulas no total.

O que vou aprender em “Depuração posterior com despejos de memória”?

Aprenda a analisar despejos de memória e relatórios de falhas para depurar problemas ocorridos no passado, sem acesso ao sistema ativo. Você pratica Production Debugging & Incident Response Playbook com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Production Debugging & Incident Response Playbook?

Nenhuma experiência prévia é necessária. Production Debugging & Incident Response Playbook no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.

Quanto tempo leva a aula “Depuração posterior com despejos de memória”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Production Debugging & Incident Response Playbook?

Sim. Cada aula de Production Debugging & Incident Response Playbook inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Depuração remota de aplicações ativas
  2. Depuração posterior com despejos de memória
  3. Técnicas de criação de perfis de memória e CPU
  4. Rastreamento distribuído para pontos críticos de latência
← Voltar para Production Debugging & Incident Response Playbook