[Solved] Given the code snippet: taskENTER_CRITICAL(); sharedCounter++; taskEXIT_CRITICAL(); What is the effect of this code on sharedCounter in a multitasking environment? | FreeRTOS

FreeRTOS - Interrupt Management

Given the code snippet:

taskENTER_CRITICAL();
sharedCounter++;
taskEXIT_CRITICAL();

What is the effect of this code on sharedCounter in a multitasking environment?

AsharedCounter may be corrupted due to interrupts

BsharedCounter is safely incremented without interruption

CsharedCounter is reset to zero

DsharedCounter increment is delayed indefinitely

Step-by-Step Solution

Solution:

Step 1: Analyze critical section usage
taskENTER_CRITICAL() disables interrupts, preventing context switches during increment.
Step 2: Effect on sharedCounter
Increment happens atomically, so sharedCounter is safely updated without corruption.
Final Answer:
sharedCounter is safely incremented without interruption -> Option B
Quick Check:
Critical section ensures safe increment = True [OK]

Quick Trick: Critical sections make increments atomic and safe [OK]

Common Mistakes:

Master "Interrupt Management" in FreeRTOS

9 interactive learning modes - each teaches the same concept differently

More FreeRTOS Quizzes

Given the code snippet: