-
Notifications
You must be signed in to change notification settings - Fork 18k
syscall: sort environment passed to CreateProcess / CreateProcessAsUser #29530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This isn't actually a documentation bug (I see this issue just received the Documentation label) but a potential golang standard library bug for Windows platform. |
Evil machine overlords etc etc… |
This SGTM. I don't see the downside of this change. But others might disagree. Alex |
Change https://golang.org/cl/160828 mentions this issue: |
If this isn't causing any known problems, I think we should wait until Go 1.14 (and early-in-cycle). |
SGTM! |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I looked at https://github.com/golang/go/blob/go1.11.4/src/syscall/exec_windows.go#L97-L122
What did you expect to see?
I expected to see the env vars sorted alphabetically by name, with case-insensitive sort, Unicode order, without regard to locale.
What did you see instead?
The code does not sort the environment variable entries. The MSDN docs state:
Note, this hasn't caused me any problems - but it seems like this could cause problems with any Windows kernel functions that expect the env to be sorted.
The text was updated successfully, but these errors were encountered: