Book Image

Linux System Programming Techniques

By : Jack-Benny Persson
5 (1)
Book Image

Linux System Programming Techniques

5 (1)
By: Jack-Benny Persson

Overview of this book

Linux is the world's most popular open source operating system (OS). Linux System Programming Techniques will enable you to extend the Linux OS with your own system programs and communicate with other programs on the system. The book begins by exploring the Linux filesystem, its basic commands, built-in manual pages, the GNU compiler collection (GCC), and Linux system calls. You'll then discover how to handle errors in your programs and will learn to catch errors and print relevant information about them. The book takes you through multiple recipes on how to read and write files on the system, using both streams and file descriptors. As you advance, you'll delve into forking, creating zombie processes, and daemons, along with recipes on how to handle daemons using systemd. After this, you'll find out how to create shared libraries and start exploring different types of interprocess communication (IPC). In the later chapters, recipes on how to write programs using POSIX threads and how to debug your programs using the GNU debugger (GDB) and Valgrind will also be covered. By the end of this Linux book, you will be able to develop your own system programs for Linux, including daemons, tools, clients, and filters.
Table of Contents (14 chapters)

Chapter 4: Handling Errors in Your Programs

In this chapter, we will learn about error handling in C programs in Linux—specifically, how to catch errors and print relevant information about them. We will also learn how to incorporate this knowledge with what we have previously learned about stdin, stdout, and stderr.

We will continue on the path of system calls and learn about a particular variable called errno. Most system calls use this variable to save specific error values when an error occurs.

Handling errors in your programs will make them more stable. Errors do occur; it's just a matter of handling them correctly. A well-handled error does not seem like an error to the end user. For example, instead of letting your program crash in some mysterious way when the hard drive is filled, it's better to catch the error and print a human-readable and friendly message about it. That way, it merely appears as information to the end user and not an error. That, in...