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

[bug] potential segfault after changing composite type definition #81

Closed
BenConnault opened this issue Mar 13, 2014 · 1 comment
Closed

Comments

@BenConnault
Copy link

Context at julia-user, including files to reproduce.

To reproduce, run:

include("segf.jl")
tt=DDCM.segf();
tt.tpi[1][1,1] 

With include("old_types.jl") in segf.jl, this returns 0.0.

With include("new_types.jl") in segf.jl, it throws sometimes a segfault, sometimes:

ERROR: no method getindex(SYSTEM: show(lasterr) caused an error
ERROR: no method Enumerate{I}(
 in showerror at repl.jl:111
 in showerror at repl.jl:66
 in anonymous at client.jl:93
 in with_output_color at util.jl:444
 in display_error at client.jl:91SYSTEM: show(lasterr) caused an error
WARNING: it is likely that something important is broken, and Julia will not be able to continue normally
@timholy
Copy link
Member

timholy commented Dec 6, 2014

This should have been fixed by the new framework for saving composite objects.

@timholy timholy closed this as completed Dec 6, 2014
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

2 participants