https://bugs.winehq.org/show_bug.cgi?id=57600
--- Comment #9 from Angel angel.narvaez@civiceye.com --- Oh man!!
It looks like my message didn't actually post :( Here's the gist of my unposted messages:
Upon further research, we don't spawn a new child process, but rather we just create a new console by using AllocConsole and redirect the stdout via freopen("CONOUT$", "w", stdout); .... I have attached a C++ application that pretty much replicates this behaviour.
What I would expect to see is that I should be able to do wine app.exe | cat or even tail -f /proc/{procid}/fd/1 ... and that should spit out the console output to my terminal.
The actual application behavior is matching in windows and wine, but for the life of me... I have no way of spitting out the Allocated Console stdout.
The only thing I can think of is line # 1403 in dlls/ntdll/unix/env.c
if (main_image_info.SubSystemType != IMAGE_SUBSYSTEM_WINDOWS_CUI) return;
I'm definitely not even remote to close to familiar with wine, but wouldn't this prevent the std handles from being initialized (and therefore I'm unable to get my console output) ??
I'm honestly just interested in getting the console output so I would love to hear your thoughts. I believe the application I attached does a good job of mimicking our app behavior where console output not printed to terminal using | cat