Reverse Engineering & Binary Analysis Basics · 课时

调试器基础（GDB、WinDbg）

学习 GDB 和 WinDbg 等调试器的核心功能，包括附加到进程和加载二进制文件。

调试器基础（GDB、WinDbg） 是 CoddyKit 上的免费 Reverse Engineering & Binary Analysis Basics 课时。这是第 1 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Reverse Engineering & Binary Analysis Basics 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Reverse Engineering & Binary Analysis Basics 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Meet Your Debugger!

Welcome to dynamic analysis! Here, we'll learn about debuggers, powerful tools that let you see a program in action.

A debugger allows you to pause a running program, inspect its internal state (like memory and registers), and even change its execution path. It's like having X-ray vision for software!

Why Debuggers for RE?

In reverse engineering, debuggers are crucial for understanding how a program behaves at runtime. While static analysis (looking at code without running it) gives you clues, dynamic analysis shows you the truth.

See actual data values as they change.
Observe which code paths are taken.
Understand interactions with the operating system.

GDB & WinDbg: Your Toolkit

We'll focus on two primary debuggers:

GDB (GNU Debugger): The standard debugger for Linux, macOS, and other Unix-like systems. It's command-line based and highly versatile.
WinDbg: A powerful debugger for Windows, often used for kernel-mode debugging and complex user-mode issues. It has both a GUI and a command-line interface.

Core Debugger Actions

Regardless of the debugger, you'll perform a few fundamental actions:

Loading a Binary: Starting a program directly under the debugger's control.
Attaching to a Process: Connecting the debugger to a program that is already running.
Inspecting State: Examining memory, registers, stack, and other program data.

Loading with GDB: Example

To load a program with GDB, you typically specify the executable on the command line. Let's compile a tiny C program first:

#include <stdio.h>

int main() {
  printf("Hello from GDB!\n");
  return 0;
}

Loading and Running in GDB

After compiling the C code (e.g., gcc -o hello hello.c), you can load it into GDB. Then, use the run command to start its execution.

GDB Commands:
gdb ./hello
(gdb) run

This will execute the program, and GDB will show you its output and then return to the GDB prompt.

Attaching to a Process with GDB

Sometimes, a program is already running, and you need to debug it on the fly. This is where attaching comes in. You'll need the program's Process ID (PID).

First, get the PID (e.g., using ps aux | grep on Linux). Then, use GDB with the -p flag:

#include <stdio.h>
#include <unistd.h>

int main() {
  printf("Program running. PID: %d\n", getpid());
  sleep(60); // Keep program alive for 60 seconds
  printf("Program exiting.\n");
  return 0;
}

GDB Attach Command

Run the previous C program in a terminal. Note its PID. Then, in another terminal, you can attach GDB to it:

GDB Command:
gdb -p <PID_OF_YOUR_PROGRAM>

Once attached, the program will pause. You can then use GDB commands to inspect its state, set breakpoints, and continue execution.

WinDbg: Loading & Attaching

WinDbg offers similar functionalities for Windows. To load a binary, you can launch WinDbg and use File > Open Executable, or use the command line: windbg.exe -o myprogram.exe.

To attach to a running process, navigate to File > Attach to a Process. You'll then see a list of running processes by name and PID, allowing you to select the target.

Quick Check!

You've learned about loading and attaching programs to debuggers. Which GDB command is used to start a program that has already been loaded into GDB?

Recap: Debugger Essentials

Great job! You've grasped the fundamental ways to get a debugger connected to a program:

Loading: Starting a new program directly under debugger control (e.g., gdb ./program then run).
Attaching: Connecting to an already active program (e.g., gdb -p <PID>).

These techniques are your entry points into dynamic analysis, allowing you to observe and manipulate programs in real-time. Next, we'll explore how to pause execution and step through code!

常见问题解答

「调试器基础（GDB、WinDbg）」课时是免费的吗？

是的 — 「调试器基础（GDB、WinDbg）」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Reverse Engineering & Binary Analysis Basics 课程的其余内容，请升级到 CoddyKit PRO。 Reverse Engineering & Binary Analysis Basics 课程共包含 4 节课。

「调试器基础（GDB、WinDbg）」这节课中我会学到什么？

学习 GDB 和 WinDbg 等调试器的核心功能，包括附加到进程和加载二进制文件。你通过在浏览器中直接运行的动手代码来练习 Reverse Engineering & Binary Analysis Basics，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Reverse Engineering & Binary Analysis Basics 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Reverse Engineering & Binary Analysis Basics 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 1 节课，共 4 节。

「调试器基础（GDB、WinDbg）」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Reverse Engineering & Binary Analysis Basics 课中编写并运行代码吗？

能。每节 Reverse Engineering & Binary Analysis Basics 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Reverse Engineering & Binary Analysis Basics