Setting breakpoints in embedded in Embedded C - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Breakpoint effect on variable value

Consider this embedded C code snippet running on a microcontroller. A breakpoint is set at the line where counter is incremented. What will be the value of counter when the program is paused at the breakpoint?

Embedded C

volatile int counter = 0;

void main() {
    while(1) {
        counter++;
        // Breakpoint set here
    }
}

A 0

B 1

C Undefined (depends on optimization)

D 2

💡 Hint

Think about when the breakpoint pauses the program in relation to the increment operation.

The breakpoint pauses execution immediately after counter++ increments the value. So counter will be 1 at the breakpoint.

❓ Predict Output

intermediate

Effect of breakpoint on timing in embedded loop

In an embedded system, a breakpoint is set inside a fast loop. What is the most likely effect on the loop's timing when the breakpoint is hit?

Embedded C

volatile int i = 0;

void main() {
    while(1) {
        i++;
        // Breakpoint here
    }
}

A Loop timing speeds up

B Loop timing remains unchanged

C Loop timing slows down significantly

D Loop stops permanently

💡 Hint

Consider what happens when the debugger pauses the CPU.

When the breakpoint is hit, the CPU pauses, so the loop timing slows down significantly.

🔧 Debug

advanced

Why does the breakpoint not hit in this embedded code?

You set a breakpoint inside this function, but the debugger never stops there. What is the most likely reason?

Embedded C

inline void fast_function() {
    // Breakpoint set here
    // Some code
}

void main() {
    while(1) {
        fast_function();
    }
}

A The function is inlined, so no separate breakpoint can be set

B The debugger is not connected properly

C The microcontroller does not support breakpoints

D The breakpoint is set on a comment line

💡 Hint

Think about what 'inline' means for function code in embedded systems.

Inline functions are expanded at compile time, so no separate code exists at the breakpoint line for the debugger to stop on.

❓ Predict Output

advanced

Output when breakpoint is set on volatile variable update

Given this embedded C code, a breakpoint is set on the line updating flag. What will be the value of flag when the program pauses at the breakpoint?

Embedded C

volatile int flag = 0;

void main() {
    flag = 1; // Breakpoint here
    while(1) {}
}

A 1

B Undefined behavior

C Program crashes

D 0

💡 Hint

Consider when the breakpoint pauses relative to the assignment.

The breakpoint pauses after flag is assigned 1, so its value is 1.

🧠 Conceptual

expert

Why might setting a breakpoint in optimized embedded code fail?

In highly optimized embedded code, setting a breakpoint on a specific source line sometimes does not pause execution there. What is the main reason for this behavior?

A Debugger software is incompatible with the microcontroller

B Embedded systems do not support breakpoints

C Breakpoints only work on function entry points

D Compiler optimization removes or rearranges code, so the source line does not map directly to machine instructions

💡 Hint

Think about how compiler optimization changes the code layout.

Optimizations can inline, remove, or reorder code, so the debugger cannot always match source lines to actual instructions.

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