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

0.5.0-dev segfaults on bad input #17548

Closed
ethomag opened this issue Jul 22, 2016 · 5 comments
Closed

0.5.0-dev segfaults on bad input #17548

ethomag opened this issue Jul 22, 2016 · 5 comments
Labels
upstream The issue is with an upstream dependency, e.g. LLVM

Comments

@ethomag
Copy link
Contributor

ethomag commented Jul 22, 2016

$ ./julia
               _
   _       _ _(_)_     |  A fresh approach to technical computing
  (_)     | (_) (_)    |  Documentation: http://docs.julialang.org
   _ _   _| |_  __ _   |  Type "?help" for help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 0.5.0-pre+5606 (2016-07-21 19:23 UTC)
 _/ |\__'_|_|_|\__'_|  |  Commit 5fe9e53 (0 days old master)
|__/                   |  x86_64-linux-gnu

julia> xxx

signal (11): Segmentation fault
while loading no file, in expression starting on line 0
jl_f_tuple at /home/ethomag/julia/src/builtins.c:648
eval_user_input at ./REPL.jl:74
jl_call_method_internal at /home/ethomag/julia/src/julia_internal.h:177 [inlined]
jl_apply_generic at /home/ethomag/julia/src/gf.c:2034
macro expansion at ./REPL.jl:92 [inlined]
#3 at ./event.jl:46
jl_call_method_internal at /home/ethomag/julia/src/julia_internal.h:177 [inlined]
jl_apply_generic at /home/ethomag/julia/src/gf.c:2034
jl_apply at /home/ethomag/julia/src/julia.h:1394 [inlined]
start_task at /home/ethomag/julia/src/task.c:253
unknown function (ip: 0xffffffffffffffff)
Allocations: 1379068 (Pool: 1378193; Big: 875); GC: 0
Segmentation fault (core dumped)
@Keno
Copy link
Member

Keno commented Jul 22, 2016

@JeffBezanson saw this earlier as well. It appears to be an instance of #17288.

@c42f
Copy link
Member

c42f commented Jul 22, 2016

I just ran into this as well - @vtjnash it seems that something from the #17518 merge caused this as reverting to 1fcb81c has worked around it for me.

I'm amused by the following:

julia> x

signal (11): Segmentation fault
...

@tkelman
Copy link
Contributor

tkelman commented Jul 22, 2016

How is it possible these slipped by without causing test failures?

@yuyichao yuyichao added the upstream The issue is with an upstream dependency, e.g. LLVM label Jul 22, 2016
@yuyichao
Copy link
Contributor

Dup of #17288

@c42f
Copy link
Member

c42f commented Jul 22, 2016

@tkelman good question! I only had time for a quick look, but it seemed oddly specific to a code path involving REPL pretty printing of errors, and this isn't something you hit if you run the tests unattended.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream The issue is with an upstream dependency, e.g. LLVM
Projects
None yet
Development

No branches or pull requests

5 participants