Bird
0
0

Given this FreeRTOS trace output snippet showing task switch times, what bug can runtime monitoring help detect?

medium📝 Command Output Q13 of 15
FreeRTOS - Debugging and Monitoring
Given this FreeRTOS trace output snippet showing task switch times, what bug can runtime monitoring help detect?
TaskA switched out at 100ms
TaskB switched in at 100ms
TaskA switched in at 105ms
TaskB switched out at 110ms
ATask switch times overlap causing resource conflicts
BTaskA is starving and never runs
CTaskB runs longer than expected causing timing issues
DNo bug, tasks switch correctly
Step-by-Step Solution
Solution:
  1. Step 1: Analyze task switch timing

    TaskB runs from 100ms to 110ms (10ms), TaskA runs from 105ms to 105ms (0ms), overlapping occurs.
  2. Step 2: Identify timing issue

    TaskB runs longer than expected, overlapping TaskA's scheduled run, causing timing problems.
  3. Final Answer:

    TaskB runs longer than expected causing timing issues -> Option C
  4. Quick Check:

    Overlapping run times = timing bug [OK]
Quick Trick: Look for overlapping task run times in trace output [OK]
Common Mistakes:
  • Ignoring overlapping times
  • Assuming no bug if tasks switch
  • Confusing starvation with timing overlap

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More FreeRTOS Quizzes