http://bugs.winehq.org/show_bug.cgi?id=19668
--- Comment #7 from Jason Edmeades us@edmeades.me.uk 2012-11-29 17:17:22 CST --- So I spent some time investigating this, and independantly arrived at the conclusion that Dan did with pretty much the same patch - I dont think this is the cause of the devenv crash. A long time ago, there was a problem when cmd.exe launched a Linux compiled app (e.g. notepad) but thats been fixed a while
So to sum up, I tried the following combination, each from a command line
1. Running interactively from command prompt: A- windows app flagged as gui B- windows app flagged as cui C- wines notepad Windows matches wine for A+B, and notepad matches windows GUI, ie. A+C return to command prompt immediately. B waits
2. Running in a batch program, e.g. echo before, testgui, echo done A- windows app flagged as gui B- windows app flagged as cui C- wines notepad Windows matches wine for A+B, and notepad matches windows GUI, ie. all 3 waits for the command to complete
3. Running as cmd /c program A- windows app flagged as gui B- windows app flagged as cui C- wines notepad
This is where the difference lies, and it is specifically because the code assumes that for a GUI application if the context isnt set then we are interactive and hence test scenario 1, which is wrong - If we are part of cmd /c (or /k) then we should do the same as test scenario 3.
Will send patch - no applicable tests will help here