Handle EPIPE Broken Pipe. Avoid errors like reading from a closed socket

Mr浪子相依

于 2024-07-22 02:28:36 发布

阅读量1

点赞数

文章标签： python 开发语言

In C, a broken pipe error occurs when a process tries to write to a pipe or socket that has been closed by the other end. Unlike Java, where exceptions like this can be caught in a try-catch block, C uses signals and error codes to handle such situations.

To handle a broken pipe error in C, you can use the following approaches:

1. Ignore the SIGPIPE Signal

The default behavior when a SIGPIPE signal is raised is to terminate the process. You can change this behavior by ignoring the SIGPIPE signal. This way, the write operation will return -1 and set errno to EPIPE, which you can handle in your code.

#include <signal.h>
#include <unistd.h>
#include <errno.h>
#include <stdio.h>

void handle_broken_pipe() {
    struct sigaction sa;
    sa.sa_handler = SIG_IGN;
    sa.sa_flags = 0;
    sigemptyset(&sa.sa_mask);
    sigaction(SIGPIPE, &sa, NULL);
}

int main() {
    handle_broken_pipe();

    // Example code to write to a pipe or socket
    int pipefd[2];
    if (pipe(pipefd) == -1) {
        perror("pipe");
        return 1;
    }

    // Close the read end to simulate a broken pipe
    close(pipefd[0]);

    // Attempt to write to the pipe
    ssize_t bytes_written = write(pipefd[1], "test", 4);
    if (bytes_written == -1 && errno == EPIPE) {
        printf("Caught broken pipe error\n");
    }

    return 0;
}

2. Handle the SIGPIPE Signal

Instead of ignoring the SIGPIPE signal, you can catch it and handle it appropriately in your signal handler.

#include <signal.h>
#include <unistd.h>
#include <errno.h>
#include <stdio.h>

void sigpipe_handler(int signum) {
    printf("Caught SIGPIPE signal\n");
}

void setup_sigpipe_handler() {
    struct sigaction sa;
    sa.sa_handler = sigpipe_handler;
    sa.sa_flags = 0;
    sigemptyset(&sa.sa_mask);
    sigaction(SIGPIPE, &sa, NULL);
}

int main() {
    setup_sigpipe_handler();

    // Example code to write to a pipe or socket
    int pipefd[2];
    if (pipe(pipefd) == -1) {
        perror("pipe");
        return 1;
    }

    // Close the read end to simulate a broken pipe
    close(pipefd[0]);

    // Attempt to write to the pipe
    ssize_t bytes_written = write(pipefd[1], "test", 4);
    if (bytes_written == -1 && errno == EPIPE) {
        printf("Caught broken pipe error\n");
    }

    return 0;
}

3. Check for EPIPE Error Code

When ignoring SIGPIPE, the write operation will fail with -1 and set errno to EPIPE. You can then handle this error in your code.

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

int main() {
    // Example code to write to a pipe or socket
    int pipefd[2];
    if (pipe(pipefd) == -1) {
        perror("pipe");
        return 1;
    }

    // Close the read end to simulate a broken pipe
    close(pipefd[0]);

    // Attempt to write to the pipe
    ssize_t bytes_written = write(pipefd[1], "test", 4);
    if (bytes_written == -1) {
        if (errno == EPIPE) {
            printf("Caught broken pipe error\n");
        } else {
            perror("write");
        }
    }

    return 0;
}

By using these methods, you can handle broken pipe errors in C without terminating your process.

Handling a scenario where you need to check if a socket is readable before attempting to read from it is crucial to avoid errors like reading from a closed socket. Here’s how you can approach this in C using system calls like ioctl, select, and related functions:

Using `ioctl` with `FIONREAD`

The ioctl system call with FIONREAD can be used to check the number of bytes available to read from a socket without blocking. This helps in determining if the socket is ready to be read from.

#include <stdio.h>
#include <unistd.h>
#include <sys/ioctl.h>
#include <sys/socket.h>
#include <netinet/in.h>

int is_socket_readable(int sockfd) {
    int bytes_readable;
    if (ioctl(sockfd, FIONREAD, &bytes_readable) == -1) {
        perror("ioctl");
        return 0; // Error checking readability
    }
    return (bytes_readable > 0);
}

int main() {
    int sockfd = socket(AF_INET, SOCK_STREAM, 0);
    if (sockfd == -1) {
        perror("socket");
        return 1;
    }

    // Connect, bind, or set up the socket as needed

    // Example of checking if the socket is readable
    if (is_socket_readable(sockfd)) {
        // Socket is readable, proceed with reading
        char buffer[1024];
        ssize_t bytes_read = read(sockfd, buffer, sizeof(buffer));
        if (bytes_read == -1) {
            perror("read");
            // Handle read error
        } else if (bytes_read == 0) {
            printf("Socket closed by peer\n");
            // Handle socket closed by peer
        } else {
            // Process the read data
            printf("Read %zd bytes: %s\n", bytes_read, buffer);
        }
    } else {
        printf("Socket is not readable\n");
        // Handle socket not readable
    }

    close(sockfd);
    return 0;
}

Using `select` with `FD_ISSET`, `FD_ZERO`, `FD_SET`

Another approach is to use the select function along with FD_ISSET, FD_ZERO, and FD_SET macros to check the readiness of the socket before reading. This method allows you to monitor multiple file descriptors for readability.

#include <stdio.h>
#include <unistd.h>
#include <sys/select.h>
#include <sys/time.h>
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>

int is_socket_readable(int sockfd) {
    fd_set readfds;
    FD_ZERO(&readfds);
    FD_SET(sockfd, &readfds);

    struct timeval timeout;
    timeout.tv_sec = 0; // Set timeout to zero for non-blocking check
    timeout.tv_usec = 0;

    // Use select to check if the socket is readable
    int ready = select(sockfd + 1, &readfds, NULL, NULL, &timeout);
    if (ready == -1) {
        perror("select");
        return 0; // Error checking readability
    }
    return FD_ISSET(sockfd, &readfds);
}

int main() {
    int sockfd = socket(AF_INET, SOCK_STREAM, 0);
    if (sockfd == -1) {
        perror("socket");
        return 1;
    }

    // Connect, bind, or set up the socket as needed

    // Example of checking if the socket is readable
    if (is_socket_readable(sockfd)) {
        // Socket is readable, proceed with reading
        char buffer[1024];
        ssize_t bytes_read = read(sockfd, buffer, sizeof(buffer));
        if (bytes_read == -1) {
            perror("read");
            // Handle read error
        } else if (bytes_read == 0) {
            printf("Socket closed by peer\n");
            // Handle socket closed by peer
        } else {
            // Process the read data
            printf("Read %zd bytes: %s\n", bytes_read, buffer);
        }
    } else {
        printf("Socket is not readable\n");
        // Handle socket not readable
    }

    close(sockfd);
    return 0;
}

Explanation:

ioctl(sockfd, FIONREAD, &bytes_readable): This call checks the number of bytes available for reading (bytes_readable) from the socket sockfd without blocking. If bytes_readable is greater than 0, the socket is readable.
select(sockfd + 1, &readfds, NULL, NULL, &timeout): select allows monitoring multiple file descriptors (sockfd in this case) to see if I/O is possible. FD_SET adds the socket to the set of file descriptors to be checked, and FD_ISSET checks if the socket is ready for reading.

Using these techniques, you can safely check if a socket is readable before attempting to read from it, thereby avoiding errors related to reading from closed sockets in C programming.

原创作者: u_11658127 转载于: https://blog.51cto.com/u_11658127/11524663

Mr浪子相依

关注

0
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
Handle EPIPE Broken Pipe. Avoid errors like reading from a closed socket

In C, a broken pipe error occurs when a process tries to write to a pipe or socket that has been closed by the other end. Unlike Java, where exceptions like this ...
复制链接

扫一扫