Skip to content
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

Segfault on break #11382

Closed
wildart opened this issue May 21, 2015 · 6 comments
Closed

Segfault on break #11382

wildart opened this issue May 21, 2015 · 6 comments

Comments

@wildart
Copy link
Member

wildart commented May 21, 2015

I tried to cancel script executed from command line and got a segfault.

^Cerror in running finalizer: <?::
signal (11): Segmentation fault
jl_static_show at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
jl_static_show at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
jl_static_show at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
jl_static_show at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
unknown function (ip: -763893982)
unknown function (ip: -763890736)
uv_atexit_hook at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
jl_exit at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
unknown function (ip: -763959987)
unknown function (ip: -767278272)
jl_gc_collect at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
allocobj at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
jl_alloc_array_1d at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
distance_to_manifold at /home/art/.julia/v0.3/LMCLUS/src/LMCLUS.jl:413
find_separation at /home/art/.julia/v0.3/LMCLUS/src/LMCLUS.jl:309
find_best_separation at /home/art/.julia/v0.3/LMCLUS/src/LMCLUS.jl:262
find_manifold at /home/art/.julia/v0.3/LMCLUS/src/LMCLUS.jl:129
lmclus at /home/art/.julia/v0.3/LMCLUS/src/LMCLUS.jl:67
jl_apply_generic at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
anonymous at no file:88
unknown function (ip: -763914996)
unknown function (ip: -763912499)
jl_load at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
include at ./boot.jl:245
jl_apply_generic at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
include_from_node1 at loading.jl:128
jl_apply_generic at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
process_options at ./client.jl:285
_start at ./client.jl:354
jlcall__start_17182 at /usr/bin/../lib/x86_64-linux-gnu/julia/sys.so (unknown line)
jl_apply_generic at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
unknown function (ip: 4200623)
julia_trampoline at /usr/bin/../lib/x86_64-linux-gnu/julia/libjulia.so (unknown line)
unknown function (ip: 4199613)
__libc_start_main at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
unknown function (ip: 4199667)
unknown function (ip: 0)
Segmentation fault (core dumped)
Julia Version 0.3.8
Commit 79599ad (2015-04-30 23:40 UTC)
Platform Info:
  System: Linux (x86_64-linux-gnu)
  CPU: Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz
  WORD_SIZE: 64
  BLAS: libopenblas (NO_LAPACK NO_LAPACKE DYNAMIC_ARCH NO_AFFINITY Sandybridge)
  LAPACK: liblapack.so.3
  LIBM: libopenlibm
  LLVM: libLLVM-3.3
@ScottPJones
Copy link
Contributor

I've run into this as well (yesterday, on Mac OS X)

@yuyichao
Copy link
Contributor

This seems to happen all the time and I think it is related/the same with #1468 and/or #5399

@stevengj
Copy link
Member

The only reasonable solution is to disable sigint in every ccall (#2622), I think. This is mainly just waiting for someone to implement it.

@JeffBezanson
Copy link
Member

👎. Doing something to every ccall is just way too heavy-handed. Also I don't think it would fix this issue. I think the problem is that exit_on_sigint ignores the signal-deferring mechanism:

void sigint_handler(int sig, siginfo_t *info, void *context)
{
    if (exit_on_sigint) jl_exit(0);
    if (jl_defer_signal) {
        jl_signal_pending = sig;

@JeffBezanson
Copy link
Member

@wildart see if that helps.

@wildart
Copy link
Member Author

wildart commented May 25, 2015

Sorry, I could not reproduce it neither before nor after. These faults happened sometimes in 0.3.x, but 0.4 experience is more stable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants