-
-
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
Crash right before Stack Overflow with ntuple
construction
#17110
Comments
This one should be fixed after #17707 |
This specific example yes but probably not the more general segfault at |
Of course, but that is also reported in #17109, right? |
Oh sorry, I mixed the two of them up. |
I had initially opened this separate from #17109 because there were some suggestive differences in the stack traces between the two. In other words, #17109 crashes in I suppose it might be possible that they are still the same (not knowledgeable enough myself to know if the GC finalizer would be called during stack unwind after a stack overflow), but regardless if this variant of the bug is no longer reproducible, I suppose it could be closed. |
Why do you say that? |
I was assuming this was the case based on this line from the stack trace:
But also, in this case the Julia process crashes with an uncaught exception, which is different than the segfault in #17109 (though, again, that doesn't mean they don't both have the same root cause). |
Closing as dup of #17109; this manifestation should be fixed. |
This is occurring on v0.5 (Could be related to #17109)
If calling
ntuple(f::F, n::Int)
withn
leads to a Stack Overflow, then calling withn-1
leads to a crash. For example:The text was updated successfully, but these errors were encountered: