-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
long tuple problems #11320
Comments
Thanks for opening an issue on this! |
Just to clarify. The branch I had to reproduce this already has the fix for #11313. A version before it is fixed seems to hit that SegFault first and end up with a slightly different backtrace pattern. |
OK. The issue is that for a tuple longer than At the least an overflow check for offset would be helpful. A real solution will probably be related to #11321. Should also be related to #10380 (which is the reason such a huge data structure is created.) @JeffBezanson Might also be related to #11187 @Keno (although this one is not limited to codegen....) |
I'm glad this one seems to be GC free LOL..... Nonetheless, thanks @carnaval, your debugging techniques works =). |
…field offset/size overflow. Improve JuliaLang#11320
…field offset/size overflow. Improve JuliaLang#11320
…field offset/size overflow. Improve JuliaLang#11320
i'm not sure where to report the issue discussed here. my original problem is complex to reproduce, but executing julia> vcat([(symbol(i), [symbol(i/7.0), string(i)]) for i in 1:10000]...)
ERROR: OverflowError()
in anonymous at no file triggers the same error in trunk (commit cf6b3c3). also, running a smaller version (1000) works and the larger as above then works. (not sure that's clear - the above is reliably giving an error only if it's the first command run after julia starts). |
Fixed by #13147 |
Minimum working example
Segfault in GC and is possibly an GC issue so the full backtrace is not that interesting...
Trace before gc fires
This is arguably not a good thing to do but is actually what is done in
showerror(::IO, ::MethodError)
for a long argument list.Edit: This is not a stack overflow because that would be #11321 and it is much slower and would raise a
StackOverflowError
instead of a SegFault.Mailing list link: https://groups.google.com/forum/#!topic/julia-dev/BLvIjoiJtaI
@ScottPJones
@carnaval
The text was updated successfully, but these errors were encountered: