c++ - CreateProcess和重定向输出

有2个应用。
AppCMD是一个命令行应用程序，而AppMAIN用一些命令行参数启动AppCMD。
不幸的是，AppMAIN似乎不能很好地处理AppCMD的输出，并且出现了问题。

我想记录对AppCMD的调用及其输出，以查看发生了什么。

为此，我想用另一个二进制AppCMD替换AppWRAP，该二进制AppCMD将调用转发到重命名的AppWRAP并记录其输出。AppCMD应该像一个透明的中间人。

为了进行测试，我编写了一个简单的AppWrap，仅输出它的命令行参数:

#include <iostream>

using namespace std;

int main(int argc, char *argv[])
{
    cout << "#### Hello, I'm the test binary that wants to be wrapped." << endl;

    if (argc < 2) {
        cout << "#### There where no command line arguments." << endl;
    }
    else {
        cout << "#### These are my command line arguments:";
        for (int i = 1; i < argc; ++i) cout << " " << argv[i];
        cout << endl;
    }

    cout << "#### That's pretty much everything I do ... yet ;)" << endl;

    return 0;
}

我遵循MSDN: Creating a Child Process with Redirected Input and Output来实现ReadFile，但是由于它不返回，所以我被卡住了，我不知道为什么:

#include <iostream>
#include <sstream>
#include <Windows.h>


using namespace std;


const string TARGET_BINARY("TestBinary.exe");
const size_t BUFFSIZE = 4096;

HANDLE in_read        = 0;
HANDLE in_write       = 0;
HANDLE out_read       = 0;
HANDLE out_write      = 0;

int main(int argc, char *argv[])
{
    stringstream call;

    cout << "Hello, I'm BinTheMiddle." << endl;

//-------------------------- CREATE COMMAND LINE CALL --------------------------

    call << TARGET_BINARY;
    for (int i = 1; i < argc; ++i) {
        call << " " << argv[i];
    }

    cout << "Attempting to call '" << call.str() << "'" << endl;

//------------------------------ ARRANGE IO PIPES ------------------------------

    SECURITY_ATTRIBUTES security;
    security.nLength              = sizeof(SECURITY_ATTRIBUTES);
    security.bInheritHandle       = NULL;
    security.bInheritHandle       = TRUE;
    security.lpSecurityDescriptor = NULL;

    if (!CreatePipe(&out_read, &out_write, &security, 0)) {
        cout << "Error: StdoutRd CreatePipe" << endl;
        return -1;
    }
    if (!SetHandleInformation(out_read, HANDLE_FLAG_INHERIT, 0)) {
        cout << "Stdout SetHandleInformation" << endl;
        return -2;
    }
    if (!CreatePipe(&in_read, &in_write, &security, 0)) {
        cout << "Stdin CreatePipe" << endl;
        return -3;
    }
    if (!SetHandleInformation(in_write, HANDLE_FLAG_INHERIT, 0)) {
        cout << "Stdin SetHandleInformation" << endl;
        return -4;
    }
//------------------------------ START TARGET APP ------------------------------

    STARTUPINFO         start;
    PROCESS_INFORMATION proc;

    ZeroMemory(&start, sizeof(start));
    start.cb         = sizeof(start);
    start.hStdError  = out_write;
    start.hStdOutput = out_write;
    start.hStdInput  = in_read;
    start.dwFlags    |= STARTF_USESTDHANDLES;

    ZeroMemory(&proc, sizeof(proc));

    // Start the child process.
    if (!CreateProcess(NULL, (LPSTR) call.str().c_str(), NULL, NULL, TRUE,
                       0, NULL, NULL, &start, &proc))
    {
        cout << "CreateProcess failed (" << GetLastError() << ")" << endl;
        return -1;
    }

    // Wait until child process exits.
    WaitForSingleObject(proc.hProcess, INFINITE);
    // Close process and thread handles.
    CloseHandle(proc.hProcess);
    CloseHandle(proc.hThread);

//----------------------------------- OUTPUT -----------------------------------

    DWORD dwRead;
    CHAR  chBuf[127];

    while (ReadFile(out_read, chBuf, 127, &dwRead, NULL)) {
        cout << "Wrapped: " << chBuf << endl;
    }

    return 0;
}

似乎正在等待ojit_code返回。有人可以发现我在做什么吗？

我这样称呼二进制文件:

> shell_cmd_wrapper.exe param1 param2

这是控制台输出，但二进制文件不返回。

Hello, I'm BinTheMiddle.
Attempting to call 'TestBinary.exe param1 param2'
Wrapped:#### Hello, I'm the test binary that wants to be wrapped.
#### These are my command line arguments: param1 param2
#### That'sD
Wrapped: pretty much everything I do ... yet ;)
s to be wrapped.
#### These are my command line arguments: param1 param2
#### That'sD

(请忽略我不清除缓冲区)

最佳答案

调用out_write之后，关闭in_read和CreateProcess句柄。否则，当管道为空时，ReadFile上的out_read将会阻塞，因为即使在 child 退出后，仍然有潜在的作者-当前进程中的out_write句柄。

同样，正如哈里·约翰斯顿(Harry Johnston)在评论中指出的那样，在从管道读取之前等待进程退出可能会导致死锁。如果管道填满，该子项将在WriteFile上阻塞。