Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6871793
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T03:50:52+00:00 2026-05-27T03:50:52+00:00

I wrote a little program using fork to create new processes which use pipe

  • 0

I wrote a little program using fork to create new processes which use pipes to communicate. Applying defensive programming, I check every return value. If a return value indicates that something went wrong, I want to free all resources, close all pipes and the parent process to wait on it’s child processes to terminate. Now, what’s the best way to bail out if an error occurs?

At the moment, I’m doing it this way:

    /* initialize pipes */
if(pipe(p1fd) == -1) {
    (void) printError("Could not init pipe 1");
    exit(EXIT_FAILURE);
}
if(pipe(p2fd) == -1) {
    (void) printError("Could not init pipe 2");
    (void) close(p1fd[0]);
    (void) close(p1fd[1]); 
    exit(EXIT_FAILURE);
}

switch (pid = fork()) {
    case -1: 
        (void) printError("Could not fork");
        (void) close(p1fd[0]);
        (void) close(p1fd[1]);
        (void) close(p2fd[0]);
        (void) close(p2fd[1]);  
        exit(EXIT_FAILURE);
        break;
    case 0: /* child process */
        break;
    default: /* parent process */       
        break;
}   

This gets quite cumbersome if one needs more resources. Another way I thought of was providing a bailout function that simply closes all pipes without caring if the pipes have actually been opened (same for freeing memory and calling wait on child processes). But then, all variables needed in such a bail out function would have to be global, since some of the pipes are passed on to different child processes/functions.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T03:50:53+00:00Added an answer on May 27, 2026 at 3:50 am

    You could use goto to avoid repeating the same code in each of the failure branches:

    if (pipe(p1fd) == -1) {
        printError("Could not init pipe 1");
        goto pipe1_fail;
    }
    
    if (pipe(p2fd) == -1) {
        printError("Could not init pipe 2");
        goto pipe2_fail;
    }
    
    switch (pid = fork()) {
        case -1: 
            printError("Could not fork");
            goto fork_fail;
    
        case 0: /* child process */
            ...
            exit(...);
    
        default: /* parent process */       
            ...
            exit(...);
    }
    
    fork_fail:
    close(p2fd[0]);
    close(p2fd[1]);
    
    pipe2_fail:
    close(p1fd[0]);
    close(p1fd[1]);
    
    pipe1_fail:
    exit(EXIT_FAILURE);
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I wrote a little program that solves 49151 sudoku's within an hour for an
I've been playing with Python for a while and wrote a little program to
I wrote a nice little program. At some point, it is required to load
I wrote a little Haskell program to find the area of a triangle, primarily
i wrote a little test programm which queries the status servlet of a tomcat
i wrote a little addin, which does some formatting of my C# code. in
I wrote a very short program that parses a program using python and converts
I worte a little Web Proxy program that uses a TcpListener, which listen on
I wanna write a little c++ program using libcurl. It's for a school project
I wrote a little program to calculate the first 18 triples (x,y,z) with x<y<z

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.