Setting breakpoints in embedded in Embedded C - Step-by-Step Execution

Concept Flow - Setting breakpoints in embedded

Write Embedded C Code

↓

Load Code into Debugger

↓

Set Breakpoint at Line

↓

Run Program

↓

Program Stops at Breakpoint

↓

Inspect Variables/Memory

↓

Step Through Code or Continue

↓

Repeat or Remove Breakpoint

↓

End Debugging

This flow shows how to set a breakpoint in embedded C code, run the program, and pause execution to inspect and debug.

Execution Sample

Embedded C

int main() {
  int x = 0;
  x = x + 1; // breakpoint here
  return x;
}

Simple embedded C program where a breakpoint is set on the line that increments x.

Execution Table

Step	Action	Code Line	Breakpoint Hit?	Variable x	Debugger State
1	Start program	int main() {	No	undefined	Ready
2	Declare x	int x = 0;	No	0	Running
3	Breakpoint hit before increment	x = x + 1; // breakpoint here	Yes	0	Paused
4	Inspect x	N/A	Yes	0	Paused - Inspecting
5	Step over increment	x = x + 1;	No	1	Paused
6	Continue execution	return x;	No	1	Running
7	Program ends	}	No	1	Stopped

💡 Program ends after return statement, debugger stops.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	Final
x	undefined	0	0	1	1

Key Moments - 3 Insights

Why does the debugger pause before x is incremented?

Because the breakpoint is set on the line 'x = x + 1;', the debugger stops before executing that line, as shown in execution_table step 3.

Why is x still 0 when the breakpoint is hit?

At the breakpoint, the line hasn't executed yet, so x remains 0. After stepping over (step 5), x becomes 1.

What happens if you continue without stepping over?

The program runs to the end without pausing again, as shown in execution_table step 6 and 7.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of x when the breakpoint is first hit?

A 0

B 1

C undefined

D Cannot tell

💡 Hint

Check execution_table row 3 under 'Variable x' column.

At which step does the variable x change from 0 to 1?

A Step 4

B Step 5

C Step 3

D Step 6

💡 Hint

Look at execution_table rows 3 and 5 for 'Variable x' values.

If you remove the breakpoint, what happens to the debugger state in step 3?

A Paused

B Stopped

C Running

D Error

💡 Hint

Without breakpoint, program runs without pause; see 'Breakpoint Hit?' column in execution_table.

Concept Snapshot

Setting breakpoints in embedded C:
- Place breakpoint on code line to pause execution
- Run program in debugger
- Program stops before executing breakpoint line
- Inspect variables and step through code
- Continue or remove breakpoints to resume
- Helps find bugs by checking program state

Full Transcript

This visual execution shows how to set a breakpoint in embedded C code. The program starts and declares variable x as 0. When running, the debugger pauses at the breakpoint line before incrementing x. At this point, x is still 0. After stepping over the line, x becomes 1. Continuing runs the program to the end. This process helps inspect program state and debug embedded code effectively.