-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Strange bug(Segmentation fault: 11) solely existed in julia v1.0 #31240
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
Please always post an excerpt of the stacktrace so that people can triage if it is in the area of expertise.
You can also try a debug build with assertions enabled, to narrow down the cause. Furthermore if you can't reduce it to a MWE on your own please post a Manifest.toml that once can use to get the the same packages as you do and a script on how to trigger the segfault. |
The code path that could lead to that assertion failure is going away shortly (in #31191), because it has known issues |
Now I've removed the usage of state monads via bootstrap that automatically generated inline codes. Unfortunately, the problem still exist. I found that in MacOS the error message is quite short and clean:
I searched this, and I found some other cases a bit similar to mine. GiovineItalia/Gadfly.jl#1243 All of the problematic repos depends on DataFrames.jl... |
The code is reported fixed in more recent version (only seen in v1.0.x) |
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
This is previously posted at https://discourse.julialang.org/t/strange-bug-segmentation-fault-11-solely-existed-in-julia-v1-0/21392 .
It seems that no one would help with this.
I know it's quite difficult for it seems to be reproduced only if a project depends on both DataFrames.jl and MLStyle.jl .
CI: https://travis-ci.org/queryverse/Query.jl/jobs/500796102
codes: https://github.com/thautwarm/Query.jl/tree/12a1d3c214f42bb63bd18aaa936f127798d74f46
The text was updated successfully, but these errors were encountered: