https://bugs.winehq.org/show_bug.cgi?id=40935
Bug ID: 40935 Summary: CreateProcess returns empty handler Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: poida.catalin@gmail.com CC: erich.e.hoover@wine-staging.com, michael@fds-team.de, sebastian@fds-team.de Distribution: ---
Hope this is the right place to place this bug.
For a simple and fast example, use the one from here: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682512(v=vs.85).a...
Problem: After calling CreateProcess, the PROCESS_INFORMATION is empty with no handlers at all (everything is initialized with 0), GetLastError() is 0, the process is created and executed, but we have no way of knowing when it ends cause there is no handler.
Compiled using vs9 on Win7 prof. Works great. Executed on linux using wine (tried with 1.6 and winehq-staging), runs but the handlers are empty.
https://bugs.winehq.org/show_bug.cgi?id=40935
dfroze poida.catalin@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |-unknown Version|unspecified |1.9.13 Product|Wine-staging |Wine
https://bugs.winehq.org/show_bug.cgi?id=40935
--- Comment #1 from Sebastian Lackner sebastian@fds-team.de --- The example is working fine here (compiled with i686-w64-mingw32-gcc). I tested with Wine 1.9.13, but I would expect the same result with 1.6. Wine also uses CreateProcess internally and such a critical error would render basically all applications useless.
Are you by any chance passing a Linux path to CreateProcess? This would explain the problem because it is not fully supported (yet). Otherwise, please provide more details how exactly to reproduce this issue, and which fields are not set as expected.
https://bugs.winehq.org/show_bug.cgi?id=40935
--- Comment #2 from dfroze poida.catalin@gmail.com --- (In reply to Sebastian Lackner from comment #1)
The example is working fine here (compiled with i686-w64-mingw32-gcc). I tested with Wine 1.9.13, but I would expect the same result with 1.6. Wine also uses CreateProcess internally and such a critical error would render basically all applications useless.
Are you by any chance passing a Linux path to CreateProcess? This would explain the problem because it is not fully supported (yet). Otherwise, please provide more details how exactly to reproduce this issue, and which fields are not set as expected.
There is no problem with the path. For example I am testing it by running ls command in the example and in both cases (linux path and win path), i receive the output from ls
https://bugs.winehq.org/show_bug.cgi?id=40935
--- Comment #3 from dfroze poida.catalin@gmail.com --- I've tested with i686-w64-mingw32-gcc as well. But same results. It compiles, it runs, it displays the result from the command run in CreateProcess, but the PROCESS_INFORMATION is still empty.
Is there anything that I should install or set in order to get more informations?
https://bugs.winehq.org/show_bug.cgi?id=40935
--- Comment #4 from Sebastian Lackner sebastian@fds-team.de --- (In reply to dfroze from comment #3)
Is there anything that I should install or set in order to get more informations?
As already mentioned, for Linux programs (including the Linux "ls" command) this is kinda expected. They are not launched with Wine, which means Wine has no control and they run independently.
It would be interesting to know if you have found a possibility to reproduce this with a Windows or Wine program - for example winecfg.exe, wineconsole.exe.
https://bugs.winehq.org/show_bug.cgi?id=40935
--- Comment #5 from dfroze poida.catalin@gmail.com --- Thank you for the fast reply and I sorry, it seams I didn't understood what exactly you meant before.
You are right, if it is a process such as winecfg.exe (or notepad.exe), then there doesn't seem to be any problem.
One last question, when do you think there might be support for this?
https://bugs.winehq.org/show_bug.cgi?id=40935
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|CreateProcess returns empty |CreateProcess returns empty |handler |PROCESS_INFORMATION when | |starting UNIX process
--- Comment #6 from Sebastian Lackner sebastian@fds-team.de --- Thanks for confirming that this is a problem with UNIX processes only. Unfortunately I am not aware of anyone working on this at the moment.
May I ask why exactly you need this feature? For interaction with native UNIX programs, the preferred way is to compile your application with winegcc, and then to directly use fork()/exec().
https://bugs.winehq.org/show_bug.cgi?id=40935
--- Comment #7 from dfroze poida.catalin@gmail.com --- (In reply to Sebastian Lackner from comment #6)
May I ask why exactly you need this feature? For interaction with native UNIX programs, the preferred way is to compile your application with winegcc, and then to directly use fork()/exec().
Unfortunately I can't say much. The application uses other non-binary program such as python, perl, etc. to run various scripts. But now that I understand the main problem I can find a way around it.
https://bugs.winehq.org/show_bug.cgi?id=40935
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |leslie_alistair@hotmail.com
-
wine-bugs＠winehq.org