We've had two reports in the past year that CryptAcquireContextW failed; but without the Windows error code it's hard to know what's going on.
Details
Diff Detail
Event Timeline
Looks good to me, but since this is in the LLVMSupport library, you should probably add llvm-commits to the subscriber list.
LGTM with a nit.
Also, I am really curious to know why CryptAcquireContext fails in those cases!
lib/Support/Windows/Process.inc | ||
---|---|---|
421 | msg should be Msg for style conventions. |
Ah, right, I should have. But I'm not seeing how to add subscribers post-facto.
Me too. Once is a fluke, twice is a trend. Probably some obscure system-resource problem but it would be nice to be sure.
lib/Support/Windows/Process.inc | ||
---|---|---|
421 | The prevailing style in this file is for lowercase parameter names, but I guess we gotta start somewhere! |
Also, I am really curious to know why CryptAcquireContext fails in those cases!
Me too. Once is a fluke, twice is a trend. Probably some obscure system-resource problem but it would be nice to be sure.
I'm out of the office this week, so can't test, but I'm pretty sure you can reproduce this by spawning clang in an environment where the SYSTEMROOT environment variable has not been propagated (or by running it from a cmd window after typing "set SYSTEMROOT=".
msg should be Msg for style conventions.