-
-
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
Missed stackoverflow on large tuple due to lack of stack probing #36170
Comments
The issue is that this allocates a huge tuple on the stack, which then skips over the guard page, so we don't see it as a stack overflow. LLVM has "probe-stack" support which could mitigate this. |
Keno
changed the title
Segfault with a large nested tuple
Missed stackoverflow on large tuple due to lack of stack probing
Jun 6, 2020
Seems related to #28577 — we discussed |
vtjnash
added a commit
that referenced
this issue
Mar 16, 2021
vtjnash
added a commit
that referenced
this issue
Mar 18, 2021
ElOceanografo
pushed a commit
to ElOceanografo/julia
that referenced
this issue
May 4, 2021
…aLang#40068) Supported platforms are currently X86, PowerPC, and SystemZ. Fixes JuliaLang#25523 Fixes JuliaLang#36170 Closes JuliaLang#28577 Closes JuliaLang#30892
antoine-levitt
pushed a commit
to antoine-levitt/julia
that referenced
this issue
May 9, 2021
…aLang#40068) Supported platforms are currently X86, PowerPC, and SystemZ. Fixes JuliaLang#25523 Fixes JuliaLang#36170 Closes JuliaLang#28577 Closes JuliaLang#30892
johanmon
pushed a commit
to johanmon/julia
that referenced
this issue
Jul 5, 2021
…aLang#40068) Supported platforms are currently X86, PowerPC, and SystemZ. Fixes JuliaLang#25523 Fixes JuliaLang#36170 Closes JuliaLang#28577 Closes JuliaLang#30892
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I get a segfault with
rr
trace: https://s3.amazonaws.com/julialang-dumps/reports/2020-06-06T04-32-54-tkf.tar.zstIt creates a huge tuple so I'm not sure if I should be reporting this as a bug. But just in case you need yet another piece of code that is hostile to the compiler...
The text was updated successfully, but these errors were encountered: