Pipes bug when spawning non-cygwin processes
Mon Feb 24 14:46:00 GMT 2020
Thank you for your reply.
On Thu, Feb 20, 2020 at 8:01 PM Takashi Yano <firstname.lastname@example.org>
> Thanks for the test case. Indeed, this works upto cygwin 3.0.7,
> and does not work in cygwin 3.1.0 or later.
> However, I wonder what platform is your program for. This test
> case does not work also in native windows command prompt.
> Your test case works only in old cygwin pty.
I have a native graphical Windows application that relied on cygwin/mintty
providing stdout so that my printf's work.
I would contend that there's no reason for cygwin/mintty to work the same
as the native windows command prompt because the behaviour there is for it
to detach the child process. This is not the case when we run a graphical
process in a cygwin/mintty shell. The old behaviour was much welcome
because it allowed graphical applications that did not detach from the
console work just like on Linux.
I should note that there is also the odd behaviour that the child process
is created with an inherited stderr handle but when I try to write to it,
it doesn't show up anywhere. On the native windows command prompt, the
child process isn't even created with the inherit handles flag enabled.
If you want to make a program which works in cygwin pty, you
> can use cygwin g++ like:
> g++ -mwindows pipes.cpp -o pipes
> The binary built by above command works in cygwin pty, but does
> not work in cygwin console (cygwin in command prompt) even with
> cygwin 3.0.7.
This might not have worked in cygwin 3.0.07 because it's missing a
freopen("CONOUT$", "w", stdout). I had omitted this in my minimal test case
because I found that this was unnecessary when I built with Visual Studio.
If you want to make a program which works with windows console,
> you should change the code like:
> INT WinMain(HINSTANCE, HINSTANCE, PSTR, INT)
> if (!AttachConsole(ATTACH_PARENT_PROCESS)) AllocConsole();
> freopen("CONOUT$", "w", stdout);
> printf("This message used to show up in mintty cygwin v.2.11.2 shell!
> or from ssh session\n");
> return 0;
Ah, I did not now about AttachConsole(ATTACH_PARENT_PROCESS).
The application that I ship out to my users cannot force the requirement of
having cygwin, nor is compiling with cygwin g++ an option. Is there some
way to have a non-cygwin app detect the presence of cygwin pty so that it
can behave differently? When the native command prompt detaches the child
process, the child process should not really write to the parent's console
and should allocate its own instead.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin