Setting breakpoints in embedded in Embedded C - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a breakpoint in embedded programming?

A breakpoint is a marker set by the programmer to pause the program execution at a specific line or instruction. It helps to inspect the program state and find bugs.

beginner

How do you set a breakpoint in an embedded C debugger?

You set a breakpoint by selecting a line of code in the debugger interface and clicking the breakpoint button or using a command to mark that line. When the program runs, it will stop at that line.

intermediate

Why are breakpoints important in embedded systems debugging?

Breakpoints let you pause the program exactly where you want. This helps check variables, memory, and hardware states step-by-step, which is crucial because embedded systems often interact with hardware directly.

advanced

What is a hardware breakpoint and how is it different from a software breakpoint?

A hardware breakpoint uses special CPU features to stop execution without changing program code. A software breakpoint replaces an instruction with a special trap instruction. Hardware breakpoints are useful when code is in read-only memory.

intermediate

Can you set conditional breakpoints in embedded debugging? What are they?

Yes, conditional breakpoints pause execution only when a specific condition is true, like a variable reaching a value. This helps focus on specific cases without stopping every time.

What happens when a breakpoint is hit during embedded debugging?

A Program runs faster

B Program restarts from the beginning

C Program skips the breakpoint line

D Program execution pauses at the breakpoint line

When a breakpoint is hit, the program pauses so you can inspect the current state.

Which type of breakpoint does NOT modify the program code?

A Hardware breakpoint

B Conditional breakpoint

C Software breakpoint

D Line breakpoint

Hardware breakpoints use CPU features and do not change program instructions.

Why might you use a conditional breakpoint?

A To speed up program execution

B To skip debugging

C To pause only when a certain condition is met

D To permanently stop the program

Conditional breakpoints pause execution only when the specified condition is true.

Where are breakpoints usually set in embedded C debugging?

A On specific lines of source code

B Random memory addresses

C Only in header files

D In the compiler settings

Breakpoints are set on lines of source code to pause execution there.

What is a common tool used to set breakpoints in embedded development?

A Compiler

B Debugger

C Linker

D Assembler

Debuggers allow setting and managing breakpoints during program execution.

Explain how breakpoints help in debugging embedded systems.

Think about how stopping the program helps you understand what is happening inside.

Describe the difference between hardware and software breakpoints in embedded debugging.

Consider how each breakpoint type affects the program code.

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