使用重定向的I / O与子进程通信时出现死锁

时间:2018-06-24 12:38:49

标签: c++ linux pipe fork dup2

我正在编写一个程序,以编程方式与SPIN模型检查器的交互式模块进行通信。为此,我需要重定向SPIN的I / O,从程序中启动它,然后重复读取和写入它。为了测试,我使用以下简短程序,而不是旋转,该程序只有一个输入和一个输出:

#include <string> 
#include <iostream> 

using std::cin;
using std::cout;
using std::string;

void sprint(string s);
int main() 
{   
    std::string s = "empty";
    cin >> s;
    cout << "\n\tthe text is: " << s;
    return 0;    
} 

我的程序主要来自this answer,是:

#include <stdio.h>
#include <stdlib.h>
#include <string>
#include <cstring>
#include <unistd.h>
#include <errno.h>
#include <iostream>

#define PIPE_READ 0
#define PIPE_WRITE 1
#define maxReadSize 2048
using std::cout;
using std::cin;
using std::string;

int createChild(const char* szCommand, const char* aArguments, const char* szMessage);

int main()
{
    createChild("./inout" , "inout", "hello");
    return 0;
}


int createChild(const char* szCommand, const char* aArguments, const char* szMessage) 
{
    int cStdinPipe[2];
    int cStdoutPipe[2];
    int nChild;
    char nChar;
    int nResult;

    if (pipe(cStdinPipe) < 0) 
    { 
        return -1;
    }
    if (pipe(cStdoutPipe) < 0) 
    {
        close(cStdinPipe[PIPE_READ]);
        close(cStdinPipe[PIPE_WRITE]);
        return -1;
    }

    nChild = fork();
    if (0 == nChild) 
    {
        // child continues here
        cout.flush();
        close(cStdinPipe[PIPE_WRITE]);

        // redirect stdin
        if (dup2(cStdinPipe[PIPE_READ], STDIN_FILENO) == -1) 
        {
            exit(errno);
        }

        // redirect stdout
        if (dup2(cStdoutPipe[PIPE_WRITE], STDOUT_FILENO) == -1) 
        {
            exit(errno);
        }

        // all these are for use by parent only
        close(cStdinPipe[PIPE_READ]);
        close(cStdoutPipe[PIPE_READ]);
        close(cStdoutPipe[PIPE_WRITE]); 

        // run child process image
        nResult = execlp(szCommand, aArguments, NULL);

        // if we get here at all, an error occurred, but we are in the child
        // process, so just exit
        exit(nResult);
    } 
    else if (nChild > 0) 
    {
        // parent continues here
        string messageFromChild = "";
        string messageFromParent = "";
        char readBuffer[maxReadSize];
        int bytesWritten = 0;
        int bytesRead = 0;

        // close unused file descriptors, these are for child only
        close(cStdinPipe[PIPE_READ]);
        close(cStdoutPipe[PIPE_WRITE]); 

        // write to child
        if (NULL != szMessage) 
        {
            bytesWritten = write(cStdinPipe[PIPE_WRITE], szMessage, strlen(szMessage));
        }

        // read from child
        bytesRead = read(cStdoutPipe[PIPE_READ], readBuffer, maxReadSize);

        cout << "\nChild says: " << readBuffer << "\n";

        // done with these in this example program, you would normally keep these
        // open of course as long as you want to talk to the child
        close(cStdinPipe[PIPE_WRITE]);
        close(cStdoutPipe[PIPE_READ]);

        std::cout << "\n\nParent ending";
    } 
    else 
    {
        // failed to create child
        close(cStdinPipe[PIPE_READ]);
        close(cStdinPipe[PIPE_WRITE]);
        close(cStdoutPipe[PIPE_READ]);
        close(cStdoutPipe[PIPE_WRITE]);
    }
    return nChild;
}

运行该程序会导致死锁,其中子进程卡在cin上,父进程卡在read()上。删除这些调用中的任何一个都会导致两个程序都终止运行并正常退出。 write()cout都可以正常工作。

1 个答案:

答案 0 :(得分:0)

问题出在read()write()在各种流/文件/管道上的工作方式上。我的write()无法与read()交流,因为它已经写完了。 Read()依赖于EOF,它仅在管道的写入端关闭后才发送。当然,一旦关闭,它就永远消失了,我无法重新打开它来发送其他消息。

因此,我切换到命名管道(fifo),以便在每次写入后重新打开管道。