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.

Practice

1. What is the main purpose of setting a breakpoint in embedded C programming?

easy

A. To pause the program at a specific line to inspect variables and flow

B. To speed up the program execution

C. To permanently stop the program from running

D. To automatically fix errors in the code

Solution

1. Step 1: Understand what a breakpoint does

   A breakpoint pauses the program at a chosen line during debugging to check the program state.

2. Step 2: Identify the correct purpose

   Only To pause the program at a specific line to inspect variables and flow describes pausing to inspect variables and flow, which is the main use of breakpoints.

3. Final Answer:

   To pause the program at a specific line to inspect variables and flow -> Option A

4. Quick Check:

   Breakpoint = Pause and inspect [OK]

Hint: Breakpoints pause code to check variables and flow [OK]

Common Mistakes:

• Thinking breakpoints speed up code
• Confusing breakpoints with program termination
• Assuming breakpoints fix errors automatically

2. Which of the following is the correct way to set a breakpoint in an embedded C debugger?

easy

A. Write breakpoint(); in the code to set a breakpoint

B. Use the command break main.c:25 to set a breakpoint at line 25

C. Add #breakpoint 25 in the source code

D. Use set breakpoint 25 inside the C code

Solution

1. Step 1: Recognize debugger commands

   Debugger commands like break filename:line set breakpoints externally, not inside code.

2. Step 2: Identify correct syntax

   Use the command break main.c:25 to set a breakpoint at line 25 uses the correct debugger command format to set a breakpoint at line 25 in main.c.

3. Final Answer:

   Use the command break main.c:25 to set a breakpoint at line 25 -> Option B

4. Quick Check:

   Debugger command syntax = break filename:line [OK]

Hint: Use debugger commands, not code, to set breakpoints [OK]

Common Mistakes:

• Trying to set breakpoints by adding code lines
• Using incorrect syntax inside source code
• Confusing preprocessor directives with breakpoints

3. Given the following code snippet and a breakpoint set at line 5, what will the debugger do when running the program?

1: int main() {
2:   int x = 10;
3:   int y = 20;
4:   int z = x + y;
5:   z = z * 2;  // Breakpoint here
6:   return z;
7: }

medium

A. Ignore the breakpoint and run normally

B. Pause execution after line 5 executes

C. Pause execution at line 6

D. Pause execution before line 5 executes

Solution

1. Step 1: Understand breakpoint behavior

   A breakpoint pauses execution just before the specified line runs, allowing inspection before the line executes.

2. Step 2: Apply to given code

   Breakpoint at line 5 pauses before z = z * 2; runs, so execution stops right before line 5.

3. Final Answer:

   Pause execution before line 5 executes -> Option D

4. Quick Check:

   Breakpoint pauses before line runs [OK]

Hint: Breakpoints pause before the line executes [OK]

Common Mistakes:

• Thinking breakpoint pauses after line executes
• Assuming breakpoint pauses at next line
• Believing breakpoint is ignored if code is simple

4. You set a breakpoint at line 10 in your embedded C program, but the debugger never stops there. What is the most likely reason?

medium

A. The debugger does not support breakpoints

B. The breakpoint command syntax was incorrect

C. The program never reaches line 10 during execution

D. Breakpoints only work on function entry lines

Solution

1. Step 1: Consider program flow

   If the program never executes line 10, the breakpoint there will never be hit.

2. Step 2: Evaluate other options

   Debugger usually supports breakpoints and syntax errors cause errors; breakpoints work on any line, so The program never reaches line 10 during execution is most likely.

3. Final Answer:

   The program never reaches line 10 during execution -> Option C

4. Quick Check:

   Breakpoint hit only if line runs [OK]

Hint: Breakpoint triggers only if code line runs during execution [OK]

Common Mistakes:

• Assuming debugger lacks breakpoint support
• Believing breakpoints only work on function starts
• Ignoring program flow and conditions

5. You want to debug a function that is called multiple times in a loop. How can you set breakpoints to pause only on the third call of the function in embedded C?

hard

A. Set a conditional breakpoint that triggers when a call counter equals 3

B. Set three breakpoints at the function start line

C. Set a breakpoint outside the function before the loop

D. Set a breakpoint at the function end line

Solution

1. Step 1: Understand conditional breakpoints

   Conditional breakpoints pause execution only when a condition is true, such as a counter reaching 3.

2. Step 2: Apply to multiple calls

   Using a call counter variable and setting a breakpoint with condition (counter == 3) pauses only on the third call.

3. Step 3: Evaluate other options

   Setting multiple breakpoints or breakpoints outside function won't selectively pause on the third call.

4. Final Answer:

   Set a conditional breakpoint that triggers when a call counter equals 3 -> Option A

5. Quick Check:

   Conditional breakpoint = pause on specific call [OK]

Hint: Use conditional breakpoints with counters to target specific calls [OK]

Common Mistakes:

• Setting multiple breakpoints instead of one conditional
• Placing breakpoints outside the function
• Not using a counter to track calls