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

Unreachable reached #32131

Closed
denglerchr opened this issue May 24, 2019 · 3 comments
Closed

Unreachable reached #32131

denglerchr opened this issue May 24, 2019 · 3 comments

Comments

@denglerchr
Copy link

denglerchr commented May 24, 2019

Hello all,
I reached the unreachable, in both the new Julia v1.1.1 on Linux and Julia v1.1.0 on Windows. I'm not sure if this is related to #25430, if so, please delete this. Here is the reduced code, producing the error:

struct Foo{T}
    M::Array{T, 2}
end

function dostuff!(x, u::T, foo::Foo{T}) where {T}
    Msym = Symmetric(foo.M, :U)
    return 1.0
end

# Run example
myfoo = Foo(Array{Float64}(I, 3, 3))
myu = 1.0

test(x) = dostuff!(x, myu, myfoo)

# "dostuff!(1, myu, myfoo)" works for me
test(1)

And here the error message (from the Windows machine):

Unreachable reached at 000000001F502EDC

Please submit a bug report with steps to reproduce this fault, and any error messages that follow (in their entirety). Thanks.
Exception: EXCEPTION_ILLEGAL_INSTRUCTION at 0x1f502edc -- test at C:\Users\gu62lax\Dropbox\Uni\Projekte\Modules_Julia_1.0\myJLmodules\ChainDyn\examples\crash_minimal.jl:14
in expression starting at C:\Users\gu62lax\Dropbox\Uni\Projekte\Modules_Julia_1.0\myJLmodules\ChainDyn\examples\crash_minimal.jl:17
test at C:\Users\gu62lax\Dropbox\Uni\Projekte\Modules_Julia_1.0\myJLmodules\ChainDyn\examples\crash_minimal.jl:14
unknown function (ip: 000000001F502EFA)
jl_fptr_trampoline at /home/Administrator/buildbot/worker/package_win64/build/src\gf.c:1864
jl_apply_generic at /home/Administrator/buildbot/worker/package_win64/build/src\gf.c:2219
do_call at /home/Administrator/buildbot/worker/package_win64/build/src\interpreter.c:323
eval_value at /home/Administrator/buildbot/worker/package_win64/build/src\interpreter.c:411
eval_stmt_value at /home/Administrator/buildbot/worker/package_win64/build/src\interpreter.c:362 [inlined]
eval_body at /home/Administrator/buildbot/worker/package_win64/build/src\interpreter.c:755
jl_interpret_toplevel_thunk_callback at /home/Administrator/buildbot/worker/package_win64/build/src\interpreter.c:885
unknown function (ip: FFFFFFFFFFFFFFFE)
unknown function (ip: 0000000006BD887F)
unknown function (ip: FFFFFFFFFFFFFFFF)
jl_toplevel_eval_flex at /home/Administrator/buildbot/worker/package_win64/build/src\toplevel.c:764
jl_parse_eval_all at /home/Administrator/buildbot/worker/package_win64/build/src\ast.c:883
jl_load at /home/Administrator/buildbot/worker/package_win64/build/src\toplevel.c:826 [inlined]
jl_load_ at /home/Administrator/buildbot/worker/package_win64/build/src\toplevel.c:833
include at .\boot.jl:326 [inlined]
include_relative at .\loading.jl:1038
include at .\sysimg.jl:29
jl_apply_generic at /home/Administrator/buildbot/worker/package_win64/build/src\gf.c:2219
exec_options at .\client.jl:267
_start at .\client.jl:436
jl_apply_generic at /home/Administrator/buildbot/worker/package_win64/build/src\gf.c:2219
jl_apply at /home/Administrator/buildbot/worker/package_win64/build/src\julia.h:1571 [inlined]
true_main at /home/Administrator/buildbot/worker/package_win64/build/ui\repl.c:96
wmain at /home/Administrator/buildbot/worker/package_win64/build/ui\repl.c:217
__tmainCRTStartup at /usr/src/debug/mingw64-x86_64-runtime-5.0.3-1/crt\crtexe.c:329
mainCRTStartup at /usr/src/debug/mingw64-x86_64-runtime-5.0.3-1/crt\crtexe.c:212
BaseThreadInitThunk at C:\windows\System32\KERNEL32.DLL (unknown line)
RtlUserThreadStart at C:\windows\SYSTEM32\ntdll.dll (unknown line)
Allocations: 314565 (Pool: 314485; Big: 80); GC: 0
@StefanKarpinski
Copy link
Member

Thank you for the report and the lovely reduced code to produce it!

@JeffBezanson
Copy link
Member

Works for me on master. We have fixed quite a few issues like this since 1.1.

@StefanKarpinski
Copy link
Member

If you’re on 1.1 it should be easy to upgrade to 1.2 which will soon be released. Since 1.2 is non-breaking and 1.1 is not a long-term support branch that’s probably the best solution.

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

3 participants