-
-
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
LLVM errors #36902
Comments
I can reproduce this error on linux with Julia 1.5.0. julia> Iterators.flatten((tuple(nlb),Iterators.flatten( (tuple(i) for i in [unicode])))) |> collect
llvm error! Nested flatten compiles ok for julia> Iterators.flatten((tuple(1),Iterators.flatten( (tuple(i) for i in [2])))) |> collect
2-element Array{Int64,1}:
1
2 Note that collecting the inner julia> Iterators.flatten((tuple(nlb),collect(Iterators.flatten( (tuple(i) for i in [unicode]))))) |> collect
2-element Array{CombinedParsers.NIndexParser,1}:
re"(?<!\(\:)"
re"[#$(isvalid)]" The example is working as expected in 1.4.1. |
I have prepared rr traces. Interestingly, on ubuntu linux I get segmentation fault errors, rather than the errors I posted above. https://s3.amazonaws.com/julialang-dumps/reports/2020-08-04T13-22-00-mosheduminer.tar.zst rr trace for the second code block: https://s3.amazonaws.com/julialang-dumps/reports/2020-08-04T13-24-08-mosheduminer.tar.zst |
Hmm, there seems to be something wrong with those traces - they appear to be corrupted. Did something go wrong during recording? |
Not that I am aware of... I have uploaded another trace here, for the first code block. Is this one okay? |
Your traces keep ending up being exactly 76 bytes. Are you perhaps on an unsupported platform - maybe the code that is supposed to error out there broke? |
I did the traces on an ubuntu distro (zorin 15, based on 18.04). I don't know why they are corrupted... 🤷 |
@SimonDanisch complained that some of the fatal errors weren't sufficiently noisy (JuliaLang/BugReporting.jl#24), perhaps you had the same issue? |
I don't know... And as I mentioned, I got segfaults on linux, instead of the LLVM errors I got on windows. EDIT: if I recall correctly, julia did not ask me to report the bug after the segfaults on linux. |
Fixed by #39801 (confirmed by backporting that commit, since CombinedParsers.jl doesn't currently work on v1.6) |
I was playing with the
CombinedParsers.jl
library, when I got an LLVM error. Upon further attempts with related code, I got other LLVM errors. The following is the code for the first error:Running the last line (this was in the REPL) caused the following output:
The code for the second error is as follows:
Running the last line (in the REPL) caused the following output:
I am sure that the implementation of CombinedParsers is relevant here, but I have no idea how it works.
versioninfo()
output:The text was updated successfully, but these errors were encountered: