Using errno in C - Mini Project: Build & Apply

Using errno in C for Error Handling

📖 Scenario: Imagine you are writing a small C program that tries to open a file. Sometimes the file might not exist or you might not have permission to open it. The system sets a special variable called errno to tell you what went wrong.

🎯 Goal: You will write a program that tries to open a file named data.txt. If it fails, you will check the errno variable and print a friendly error message explaining why it failed.

📋 What You'll Learn

Include the errno.h and stdio.h headers

Create a FILE * variable called file and try to open data.txt in read mode

Create an int variable called errnum to store the value of errno

Use perror to print the error message if opening the file fails

Print a success message if the file opens correctly

💡 Why This Matters

🌍 Real World

In real programs, checking <code>errno</code> helps you understand why system calls or library functions fail, so you can handle errors gracefully.

💼 Career

Knowing how to use <code>errno</code> is important for system programming, debugging, and writing reliable C programs that interact with files and the operating system.

1

Include headers and declare file variable

Write the lines to include the stdio.h and errno.h headers. Then declare a variable called file of type FILE *.

C

# Include the standard input/output and errno headers
// Declare a FILE pointer called file

Hint

Use #include <stdio.h> and #include <errno.h>. Declare FILE *file;.

2

Open the file and declare errno variable

Write the line to open the file data.txt in read mode using fopen and assign it to file. Then declare an int variable called errnum and set it to errno.

C

#include 
#include 

FILE *file;

// Open data.txt in read mode and assign to file
// Declare int errnum and assign errno

Hint

Use file = fopen("data.txt", "r") and int errnum = errno;.

3

Check if file opened and print error with perror

Write an if statement to check if file is NULL. Inside the if, use perror with the message "Error opening file". Otherwise, print "File opened successfully.".

C

#include 
#include 

FILE *file;

file = fopen("data.txt", "r");
int errnum = errno;

// Check if file is NULL
// Use perror("Error opening file") if NULL
// Else print success message

Hint

Use if (file == NULL) and inside it perror("Error opening file"). Use else to print success.

4

Print the errno value and close the file if opened

After the if-else, print the value of errnum using printf with the message "errno value: %d\n". If the file is not NULL, close it using fclose(file).

C

#include 
#include 

FILE *file;

file = fopen("data.txt", "r");
int errnum = errno;

if (file == NULL) {
    perror("Error opening file");
} else {
    printf("File opened successfully.\n");
}

// Print errno value
// Close file if not NULL

Hint

Use printf("errno value: %d\n", errnum); and close the file with fclose(file); if it is not NULL.

Practice

1. What is the primary purpose of errno in C programming?

easy

A. To store error codes set by system or library functions when they fail

B. To count the number of errors in a program

C. To reset the program state after an error

D. To display error messages automatically

Solution

1. Step 1: Understand what errno stores

   errno is a global variable that stores error codes set by system or library functions when they fail.

2. Step 2: Differentiate from other options

   It does not count errors, reset program state, or display messages automatically.

3. Final Answer:

   To store error codes set by system or library functions when they fail -> Option A

4. Quick Check:

   errno stores error codes = C [OK]

Hint: Remember: errno holds error codes after failure [OK]

Common Mistakes:

• Thinking errno counts errors
• Assuming errno resets program state
• Believing errno prints messages automatically

2. Which of the following is the correct way to include errno in a C program?

easy

A. #include

B. #include

C. #include

D. #include

Solution

1. Step 1: Identify the standard header for errno

   The standard header file to use errno is <errno.h>.

2. Step 2: Verify other options

   <error.h>, <err.h>, and <errors.h> are not standard headers for errno.

3. Final Answer:

   #include <errno.h> -> Option B

4. Quick Check:

   errno header = <errno.h> [OK]

Hint: Use #include to access errno [OK]

Common Mistakes:

• Using wrong header files
• Forgetting to include errno.h
• Confusing with similar-sounding headers

3. What will the following C code print if the file nonexistent.txt does not exist?

#include <stdio.h>
#include <errno.h>
#include <string.h>

int main() {
    FILE *f = fopen("nonexistent.txt", "r");
    if (!f) {
        printf("Error: %s\n", strerror(errno));
    }
    return 0;
}

medium

A. Error: No such file or directory

B. Error: Permission denied

C. Error: File exists

D. Error: Unknown error

Solution

1. Step 1: Understand fopen failure and errno

   When fopen fails to open a non-existing file for reading, it sets errno to indicate the error, usually ENOENT meaning "No such file or directory".

2. Step 2: Use strerror to get error message

   strerror(errno) converts the error code to a readable string, which will be "No such file or directory".

3. Final Answer:

   Error: No such file or directory -> Option A

4. Quick Check:

   fopen missing file error = "No such file or directory" [OK]

Hint: fopen missing file sets errno to ENOENT message [OK]

Common Mistakes:

• Assuming errno is zero without checking fopen result
• Confusing error messages for different errors
• Not including string.h for strerror

4. Identify the error in this code snippet that uses errno:

#include <stdio.h>
#include <errno.h>
#include <string.h>

int main() {
    errno = 0;
    FILE *f = fopen("file.txt", "r");
    if (f == NULL) {
        perror("File open error");
    }
    if (errno != 0) {
        printf("Error code: %d\n", errno);
    }
    return 0;
}

medium

A. Using perror instead of strerror is incorrect

B. Setting errno to 0 before fopen is unnecessary

C. Checking errno after fopen without checking fopen result first

D. Not closing the file pointer after fopen

Solution

1. Step 1: Analyze errno usage after fopen

   errno should only be checked if the function indicates failure. Here, errno is checked regardless of fopen result, which can be misleading.

2. Step 2: Confirm correct error checking pattern

   The correct pattern is to check if fopen returned NULL before reading errno. This code checks errno even if fopen succeeded.

3. Final Answer:

   Checking errno after fopen without checking fopen result first -> Option C

4. Quick Check:

   Check function result before errno [OK]

Hint: Always check function result before reading errno [OK]

Common Mistakes:

• Reading errno without function failure
• Confusing perror and strerror usage
• Ignoring file close after fopen

5. You want to open a file for reading and print a custom error message if it fails. Which code snippet correctly uses errno and strerror to do this?

A) FILE *f = fopen("data.txt", "r");
   if (!f) {
       printf("Error: %s\n", strerror(errno));
   }

B) errno = 0;
   FILE *f = fopen("data.txt", "r");
   if (f == NULL) {
       printf("Error: %s\n", strerror(errno));
   }

C) FILE *f = fopen("data.txt", "r");
   if (f == NULL) {
       errno = 0;
       printf("Error: %s\n", strerror(errno));
   }

D) FILE *f = fopen("data.txt", "r");
   if (f == NULL) {
       perror("Error opening file");
   }

hard

A. Option A

B. Option B

C. Option C

D. Option D

Solution

1. Step 1: Check correct error handling with errno

   Option D uses perror, which is the standard and simplest way to print a custom error message along with the error string corresponding to errno. It automatically handles errno correctly.

2. Step 2: Identify issues in other options

   Option D does not reset errno before fopen, which is less safe. Option D resets errno before fopen and checks failure, but it's generally unnecessary to reset errno before calls that set it on failure. Option D resets errno after failure, clearing the error code before printing, which is incorrect.

3. Final Answer:

   Option D -> Option D

4. Quick Check:

   Use perror for simple and correct error messages [OK]

Hint: Use perror for automatic error message printing [OK]

Common Mistakes:

• Resetting errno unnecessarily
• Resetting errno after failure
• Using strerror without valid errno