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
Original bug ID: 7088 Reporter:@Chris00 Status: acknowledged (set by @damiendoligez on 2017-04-13T11:12:05Z) Resolution: open Priority: normal Severity: minor Platform: x86_64 OS: Windows Version: 4.02.3 Category: otherlibs Monitored by:@hcarty@Chris00
Bug description
The API call system¹ documentation says "If the command interpreter is not found, returns 0 and sets errno to ENOENT." It seems that this behavior is not taken into account by the C function win_system.
Note that the Microsoft documentation referenced above is self-contradictory: it says the return value will be both 0 and -1 when cmd.exe is not found.
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.
Original bug ID: 7088
Reporter: @Chris00
Status: acknowledged (set by @damiendoligez on 2017-04-13T11:12:05Z)
Resolution: open
Priority: normal
Severity: minor
Platform: x86_64
OS: Windows
Version: 4.02.3
Category: otherlibs
Monitored by: @hcarty @Chris00
Bug description
The API call system¹ documentation says "If the command interpreter is not found, returns 0 and sets errno to ENOENT." It seems that this behavior is not taken into account by the C function win_system.
¹ https://msdn.microsoft.com/en-us/library/277bwbdz.aspx
Additional information
See #349
The text was updated successfully, but these errors were encountered: