0Pricing
Reverse Engineering & Binary Analysis Basics · 강의

제어 흐름 및 함수 호출

스택 사용을 포함하여 조건부 점프, 반복문 및 함수 호출의 작동 원리를 배웁니다.

제어 흐름 및 함수 호출은(는) CoddyKit의 무료 Reverse Engineering & Binary Analysis Basics 강의입니다. 이것은 4개 중 3번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Reverse Engineering & Binary Analysis Basics 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Reverse Engineering & Binary Analysis Basics 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

Control Flow: Making Programs Smart

In assembly, instructions usually run one after another. This is called sequential execution. But real programs need to make decisions, repeat actions, and call functions.

This is where control flow comes in! It's how a program changes its execution path based on conditions, creating loops and calling subroutines.

Conditional Jumps: If-Statements

Conditional jumps are like if statements in high-level languages. They let your program execute different code blocks based on a condition.

The CMP instruction compares two values and sets CPU flags. Then, jump instructions like JE (Jump if Equal) or JNE (Jump if Not Equal) check these flags to decide whether to jump.

; Example: if (EAX == EBX) goto equal_label;
MOV EAX, 10
MOV EBX, 10
CMP EAX, EBX    ; Compare EAX and EBX
JE  equal_label ; Jump if Equal
; Code here runs if EAX != EBX
JMP end_label

equal_label:
; Code here runs if EAX == EBX

end_label:
; Program continues

More Jump Conditions

Beyond JE and JNE, many other conditional jump instructions exist to handle different comparisons:

  • JG: Jump if Greater
  • JL: Jump if Less
  • JGE: Jump if Greater or Equal
  • JLE: Jump if Less or Equal
  • JZ: Jump if Zero (often used after CMP or arithmetic)
  • JNZ: Jump if Not Zero

These instructions interpret the CPU's flags register, which stores the results of previous operations.

Building Loops in Assembly

You can create loops using conditional jumps. A loop typically involves:

  1. An initialization (e.g., setting a counter).
  2. A condition check (using CMP and a conditional jump).
  3. The loop body (instructions to repeat).
  4. An update (e.g., incrementing the counter).
  5. An unconditional jump back to the condition check.
; Example: int i = 0; while (i < 3) { i++; }
MOV ECX, 0      ; Initialize counter i = 0

loop_start:
CMP ECX, 3      ; Compare i with 3
JGE loop_end    ; Jump if i >= 3 (exit loop)

INC ECX         ; Increment i
JMP loop_start  ; Jump back to loop_start

loop_end:
; Loop has finished, continue here

The Stack: LIFO Storage

The stack is a crucial memory region used for temporary storage, especially during function calls. It operates on a LIFO (Last-In, First-Out) principle.

Think of it like a stack of plates: you can only add a new plate to the top (PUSH) or remove the top plate (POP).

  • PUSH: Decreases the stack pointer (ESP/RSP) and places data on the stack.
  • POP: Retrieves data from the top of the stack and increases the stack pointer.

Function Calls: CALL and RET

When a program needs to execute a separate block of code (a function or subroutine), it uses the CALL instruction. This is fundamental for modular programming.

  • The CALL instruction first pushes the return address (the address of the instruction immediately following CALL) onto the stack.
  • Then, it jumps unconditionally to the target function's entry point.
  • The RET instruction, typically found at the end of a function, pops the return address from the stack and jumps back to that address, resuming execution in the caller.
; Caller code:
; ... instructions
CALL my_function ; Calls the function
; ... execution continues here after my_function returns

; my_function definition:
my_function:
; ... function's body instructions
RET              ; Returns to the caller

Passing Arguments to Functions

How do functions receive input? In x86/x64 assembly, arguments are often passed via the stack or registers.

When using the stack, arguments are pushed onto the stack by the caller before the CALL instruction. The called function then accesses these arguments relative to the stack pointer (ESP/RSP) or base pointer (EBP/RBP).

The calling convention dictates the order and method of argument passing.

Local Variables and the Stack Frame

Functions also need space for their own local variables. This space is allocated on the stack within what's called a stack frame.

A stack frame is typically established by:

  1. Saving the old base pointer (PUSH EBP/RBP).
  2. Setting the new base pointer to the current stack pointer (MOV EBP, ESP/RBP, RSP).
  3. Allocating space for local variables (SUB ESP, size).

The base pointer (EBP/RBP) provides a stable reference point to access arguments and local variables within the current function.

Function Call Walkthrough

Let's see a simple C function and understand how its call, arguments, and local variables relate to assembly and the stack.

When main calls calculate_sum, the arguments 15 and 25 are pushed onto the stack. Inside calculate_sum, space for local_var is allocated on the stack. The function's return value is typically placed in a register like EAX.

#include <stdio.h>

int calculate_sum(int a, int b) {
  int local_var = a + b; // Local variable on stack
  return local_var;
}

int main() {
  int result = calculate_sum(15, 25);
  printf("Result: %d\n", result);
  return 0;
}

Quick Check: Function Calls

Understanding the stack's role in function calls is crucial for reverse engineering.

Which of the following actions occur when an x86/x64 CALL instruction is executed?

Recap: Control Flow & Functions

Great job! You've learned how programs make decisions and execute functions in assembly.

  • Conditional Jumps (JE, JNE, JG, etc.) combined with CMP enable if statements and loops.
  • The Stack is a LIFO structure critical for temporary data, managed by PUSH and POP.
  • Function Calls use CALL to push the return address and jump, and RET to pop it and return.
  • Arguments and local variables are often handled via the stack within a function's stack frame.

Understanding these concepts is vital for tracing program execution and analyzing binaries!

자주 묻는 질문

“제어 흐름 및 함수 호출” 강의는 무료인가요?

네 — “제어 흐름 및 함수 호출” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Reverse Engineering & Binary Analysis Basics 강의 전체를 잠금 해제할 수 있습니다. Reverse Engineering & Binary Analysis Basics 강의에는 총 4개의 강의가 포함되어 있습니다.

“제어 흐름 및 함수 호출”에서 뭘 배우나요?

스택 사용을 포함하여 조건부 점프, 반복문 및 함수 호출의 작동 원리를 배웁니다. 브라우저에서 직접 실행하는 실습 코드로 Reverse Engineering & Binary Analysis Basics을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Reverse Engineering & Binary Analysis Basics을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Reverse Engineering & Binary Analysis Basics은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 3번째 강의입니다.

“제어 흐름 및 함수 호출” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Reverse Engineering & Binary Analysis Basics 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Reverse Engineering & Binary Analysis Basics 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

  1. x86/x64 어셈블리 기초
  2. 레지스터 및 메모리 연산
  3. 제어 흐름 및 함수 호출
  4. 스택과 호출 규약
← Reverse Engineering & Binary Analysis Basics(으)로 돌아가기