-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Windows nightly 64-bit release exe does not start #10865
Comments
(I won't be able to debug further until tonight, but opening this up in case someone has time to debug or sees something obvious) |
Confirmed (using c384fce build downloaded from the bot minutes ago). |
Something is wrong in building the docs (python packaging is eternally aggravating) so I can't do edit: changing this line to |
Reproduced locally via This was introduced by #10832, cc @garrison, bisect log:
|
2949b1e looks good to me -- sorry about this. |
Actually, I am surprised the problem did not show up beginning with 11a0f43. But the fix looks correct. |
Fix #10865, Windows julia segfaulting without sys.dll
use LocalFree on Windows instead of free also test this on appveyor
The release exe does not start in the latest Win64 nightly (ef06211). The -debug version and both 32-bit exes are fine.
--help
does work, butjulia -e "println(\"hello, world\")"
does not.There are no messages when run in cmd, and nothing obviously wrong in Dependency Walker. I don't have gdb available right now, but in WinDbg I get:
(in WinDbg I can continue through these errors and get to the REPL prompt)
Based on seeing
jl_get_builtin_hooks
, I'm mildly suspicious of #10714, but I can't justify the suspicion since we should not be compiling the new readlink function at startup. Given the timing, the tuple overhaul seems more likely, but I did build and run ef06211 in release mode last night.The text was updated successfully, but these errors were encountered: