Error handling in files in C - Step-by-Step Execution

Concept Flow - Error handling in files

Start

↓

Open file

↓

Check if file opened?

No→Print error message

↓

Exit or handle error

↓

Read/Write file

↓

Check for errors during operation?

Yes→Print error message

↓

Exit or handle error

↓

Close file

↓

End

This flow shows opening a file, checking for errors, performing file operations, checking again for errors, then closing the file.

Execution Sample

C

#include <stdio.h>

int main() {
    FILE *fp = fopen("data.txt", "r");
    if (fp == NULL) {
        perror("Error opening file");
        return 1;
    }
    fclose(fp);
    return 0;
}

This code tries to open a file for reading, checks if it opened successfully, prints an error if not, then closes the file.

Execution Table

Step	Action	Evaluation	Result
1	Call fopen("data.txt", "r")	Returns FILE pointer or NULL	Returns NULL if file missing or no permission
2	Check if fp == NULL	fp is NULL?	Yes or No
3	If NULL, call perror	Prints error message to stderr	Error message shown
4	If NULL, return 1	Program exits with error code	Program stops
5	If not NULL, proceed	File opened successfully	Continue
6	Call fclose(fp)	Closes file	File closed
7	Return 0	Program ends successfully	Program stops

💡 Execution stops if file open fails (fp == NULL), otherwise runs to end.

Variable Tracker

Variable	Start	After fopen	After check	Final
fp	undefined	NULL or valid FILE*	NULL or valid FILE*	NULL or valid FILE*

Key Moments - 3 Insights

Why do we check if fp == NULL after fopen?

Because fopen returns NULL if it fails to open the file. Checking fp == NULL tells us if the file was opened successfully or not, as shown in execution_table step 2.

What does perror do and why is it useful?

perror prints a readable error message explaining why fopen failed. This helps understand the problem, as shown in execution_table step 3.

Why do we return 1 after perror?

Returning 1 stops the program with an error code, indicating failure. This prevents running code that assumes the file opened, as shown in execution_table step 4.

Visual Quiz - 3 Questions

Look at the execution table, what happens if fopen returns NULL?

A The program continues to read the file

B The program closes the file

C The program prints an error and stops

D The program ignores the error

💡 Hint

See execution_table rows 1 to 4 where fopen returns NULL and perror is called.

At which step does the program close the file?

A Step 6

B Step 4

C Step 2

D Step 7

💡 Hint

Check execution_table row 6 where fclose is called.

If we remove the check for fp == NULL, what will happen?

A The program will always print an error

B The program may crash or behave unexpectedly

C The program will close the file safely

D The program will return 0 immediately

💡 Hint

Refer to key_moments about why checking fp == NULL is important.

Concept Snapshot

Error handling in files in C:
- Use fopen() to open a file.
- Check if fopen returns NULL (means error).
- Use perror() to print error details.
- Return error code to stop program if needed.
- Always fclose() to close opened files.

Full Transcript

This example shows how to handle errors when working with files in C. First, we try to open a file using fopen. If fopen fails, it returns NULL. We check this immediately. If NULL, we print an error message using perror and stop the program by returning 1. If the file opens successfully, we proceed and close the file with fclose before ending the program normally. This prevents crashes or unexpected behavior when files cannot be accessed.