https://bugs.winehq.org/show_bug.cgi?id=56459
--- Comment #3 from Eric Pouech eric.pouech@gmail.com ---
I updated the spreadsheet with outcomes from wineconsole and Windows. I found that wineconsole behaved the same as running Wine from a Linux terminal but Windows behaved a but differently, which seems like a bug. I highlighted the differences with red text.
Thanks for taking care of this. I'll look into this.
My hope is that, when a process is invoked directly from the Linux terminal, we:
- Independently ensure that any printfs are flushed out to the Linux
terminal, regardless of whether they _also_ make it out to the wineconsole.
- When a process is invoked through a Linux terminal, I/O redirection is
processed by the Linux shell rather than Wine. In these cases Wine would behave as if there had been no I/O redirection requested. By extension, this would mean that I/O redirection only works like Windows does when used within wineconsole.
Combining #1 and #2 would mean that we can always get all output from a Windows program on the Linux side, regardless of Windows-style semantics, but only when a program is invoked from the Linux terminal. I'm not sure if this would break anything elsewhere but I think this would help developers while debugging because any errors logged by apps are always visible. Thoughts? Is this possible/sensible?
you may want to try: ./wine [[your exec and args]] < /dev/null 2>&1 | cat - this will ensure that no (windows) console is created (as none of fd 0,1,2 is mapped to a unix tty), but all output is redirected to linux terminal (I supposed you didn't need input from terminal in your program)