You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, thanks a lot for the great library. Recently I have been plagued by calls to the interface on the windows side. I want to create a child process with as_user_ launch, and then the standard input and standard output of the child process can be captured by the parent process. Here is my demo. In this demo, the windows side will get stuck in the read pipe, but not on the linux side. What is the reason for this? Hello_world.exe in windows outputs the user name and 'hello world', of the current process, while the script on the linux side outputs' hello world',. Part of the implementation is to refer to the test case call in the process library. I did not find out how to pass parameters on the windows side to redirect the standard output and standard error of the child process.
which version
boost 1.85.0
what i desire
i want to get the child process stdout and stderr msg through pipe in both linux and windows
Hello, thanks a lot for the great library. Recently I have been plagued by calls to the interface on the windows side. I want to create a child process with
as_user_ launch
, and then the standard input and standard output of the child process can be captured by the parent process. Here is my demo. In this demo, the windows side will get stuck in the read pipe, but not on the linux side. What is the reason for this? Hello_world.exe in windows outputs the user name and 'hello world', of the current process, while the script on the linux side outputs' hello world',. Part of the implementation is to refer to the test case call in the process library. I did not find out how to pass parameters on the windows side to redirect the standard output and standard error of the child process.which version
boost 1.85.0
what i desire
i want to get the child process stdout and stderr msg through pipe in both linux and windows
what i got
on windows side, the program was Infinite waiting
code
The text was updated successfully, but these errors were encountered: