-
-
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
Segmentation fault when running with ALWAYS_COPY_STACKS #32700
Comments
Has anyone been able to reproduce this? Without this, the whole Julia <-> Java ecosystem is broken. |
FYI @kcajf not in Julia 1.0.4 LTS version: "Without this, the whole Julia <-> Java ecosystem is broken." Still I thought the workaround (for 1.3) worked, and yes it needs fixing, and 1.4 is the milestone w/o the workaround. |
1.3 has the JULIA_COPY_STACKS environment variable: #32885. I'm not sure if that change also fixes this segfault, but a segfault is a bug so feature freeze does not apply; this can be fixed at any point. |
Thanks Stefan, I hadn't seen / tested since #32885. Testing again on |
Can we re-open this issue? I'm still experience segfaults even with JavaCall segfaults immediately for me, see here
|
Works for me:
Btw, I'm using GRAAL VM, if that changes anything... |
Wow, I feel incredibly stupid. I believe this happened because I set We should document this, any idea which section of the docs it should go in? |
I've opened #33318 to check |
In an effort to work around #31104, I have tried to build julia with
ALWAYS_COPY_STACKS
. However, I'm having into trouble when running (amongst other things) the simple multithreading example provided here https://julialang.org/blog/2019/07/multithreading.I'm on the latest master at time of writing. Before changing
ALWAYS_COPY_STACKS
, the examples run smoothly:I then modify
src/options.h
:then run
make
again.Same code as above:
The text was updated successfully, but these errors were encountered: