You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying a execute a simple dir command using ChildProcess.exec() on windows 10, the program reaches unreachable code.
An assertion fails in windows.CloseHandle() when trying to close the stderr field of ChildProcess, seemingly because CloseHandle() receives a 0 handle (tried debugging it and the error is invalid handle).
After some more testing and debugging, the above happens when ChildProcess can't find the process specified.
If the executable to be run, is in the same directory as the spawing process then everything is fine.
If not, it fails with unreachable, as above , even if the desired process to be run is in the PATH (simple path such as C:\test), and can be succesfully executed from the command line (from any cwd).
Trying to find why the assertion is hit in util.zig:42 :
assert(windows.CloseHandle(handle) !=0);
it seems that CloseHandle is given a null handle (docs specify that it must get a valid handle, I suppose 0 is not valid).
Furthermore a lot of windows processes are given null handles after the process fails to spawn such as WaitForSingleObject.
While trying a execute a simple dir command using ChildProcess.exec() on windows 10, the program reaches unreachable code.
An assertion fails in windows.CloseHandle() when trying to close the stderr field of ChildProcess, seemingly because CloseHandle() receives a 0 handle (tried debugging it and the error is invalid handle).
Reproduction code:
Stack trace:
Windows 10 and Zig version: 0.3.0+078a0a69
The text was updated successfully, but these errors were encountered: