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

Segmentation fault pressing Ctrl-C during Pkg.update() #9362

Closed
sawcordwell opened this issue Dec 15, 2014 · 4 comments
Closed

Segmentation fault pressing Ctrl-C during Pkg.update() #9362

sawcordwell opened this issue Dec 15, 2014 · 4 comments
Labels
bug Indicates an unexpected problem or unintended behavior error handling Handling of exceptions by Julia or the user packages Package management and loading

Comments

@sawcordwell
Copy link

On Julia 0.4, If I run Pkg.update() then immediately press Ctrl-C I get "ERROR: Interrupt". However, if I wait for about 5 seconds then press Ctrl-C I get a Segmentation fault. If I wait about 10 seconds, I get the error message again. I can get the same behaviour on 0.3.3.

EDIT: versioninfo()
Julia Version 0.4.0-dev+2135
Commit 6dbcf80* (2014-12-14 21:25 UTC)
Platform Info:
System: Linux (x86_64-suse-linux)
CPU: Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz
WORD_SIZE: 64
BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Haswell)
LAPACK: libopenblas
LIBM: libopenlibm
LLVM: libLLVM-3.3

@jakebolewski jakebolewski added the packages Package management and loading label Dec 15, 2014
@mlubin
Copy link
Member

mlubin commented Dec 16, 2014

I've observed this occasionally as well.

@ihnorton ihnorton added error handling Handling of exceptions by Julia or the user bug Indicates an unexpected problem or unintended behavior labels Dec 30, 2014
@ihnorton
Copy link
Member

This particular issue may be fixed by #4158, but there is also a more general question of handling interrupts in spawned processes (wherein there is a pretty hard limit to what we can realistically do - processes can do anything... I thought we had an open issue but I can't find it right now).

@jiahao
Copy link
Member

jiahao commented Feb 1, 2015

Similar to #1468? if so, then it's not just about propagating SIGABRT from spawned processes, but from external code in general.

@jakebolewski
Copy link
Member

I don't think this issue is relevant anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior error handling Handling of exceptions by Julia or the user packages Package management and loading
Projects
None yet
Development

No branches or pull requests

5 participants