-
-
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
Reliable segfault on precompiling Images #16301
Comments
I think you already reported this in #12096? Jeff fixed this then reverted the fix last summer, so I'm hoping he can look into this and explain what's broken. |
timholy
referenced
this issue
May 10, 2016
Your memory is so much better than mine. |
vtjnash
added a commit
that referenced
this issue
May 13, 2016
has-typevars is called pretty heavily during intersection and subtyping so it can be a hot-path fix lowering of TypeVar in TypeConstructor typealias expression: instead have lowering emit the correct TypeVar expression instead of mutating (aka corrupting) the immutable TypeVars in the TypeConstructor constructor avoid corrupting immutable TypeVar after building a DataType for them: instead have lowering emit the correct TypeVar expression instead of modifying them in the DataType constructor fix #12238 fix #16301
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using Images commit fbf9e98112c88355fc0b6c986995b7e9875ebcba, and
(NB: this is a debug build)
I get a segfault from
dump.c
:This doesn't happen if I set
__precompile__(false)
, or just directlyinclude("Images.jl")
.I've reproduced this on two machines, and it happens every time at the same place. It's not a complete corruption, because
The text was updated successfully, but these errors were encountered: