Looks like: https://github.com/JuliaLang/julia/issues/8550
If you can find a semi-reproducible test case and/or gdb backtrace, that would be great. On Mon, Jan 5, 2015 at 7:59 PM, Tomas Lycken <[email protected]> wrote: > I just got the following in the REPL: > > julia> module Foo > > type Bar{T} end > > end > > signal (11): Segmentation fault > unknown function (ip: -716631494) > jl_get_binding at /opt/julia-0.4/usr/bin/../lib/libjulia.so (unknown line) > jl_get_global at /opt/julia-0.4/usr/bin/../lib/libjulia.so (unknown line) > jl_module_run_initializer at /opt/julia-0.4/usr/bin/../lib/libjulia.so > (unknown line) > unknown function (ip: -716770303) > unknown function (ip: -716771435) > jl_toplevel_eval_in at /opt/julia-0.4/usr/bin/../lib/libjulia.so (unknown > line) > eval_user_input at REPL.jl:54 > jlcall_eval_user_input_42363 at (unknown line) > jl_apply_generic at /opt/julia-0.4/usr/bin/../lib/libjulia.so (unknown line) > anonymous at task.jl:96 > unknown function (ip: -716815279) > unknown function (ip: 0) > > I’ve seen segfaults a couple of times since I last built Julia from > source, but I was always too concentrated on what I was doing to try to pin > it down - but this time I wasn’t =) I hadn’t done anything in that session > except a few Pkg commands, but I couldn’t reproduce the problem either in a > fresh REPL or in one where I ran exactly the same Pkg commands in the same > sequence before doing that. Is this a known problem, or should I report it > on github? > > julia> versioninfo() > Julia Version 0.4.0-dev+2416 > Commit db3fa60 (2015-01-02 18:23 UTC) > Platform Info: > System: Linux (x86_64-linux-gnu) > CPU: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz > WORD_SIZE: 64 > BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Haswell) > LAPACK: libopenblas > LIBM: libopenlibm > LLVM: libLLVM-3.3 > > // T > >
