-
Notifications
You must be signed in to change notification settings - Fork 947
SIGSEGV in the compiler in transform.OptimizeAllocs call tree #2777
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
Labels
bug
Something isn't working
Comments
This code dereferences a nil pointer, writes into a nil map, accesses an out-of-bounds array element, and divides by zero. |
Still, it shouldn't crash at compile time. |
@ALTree does this test case come out of a fuzzer? |
aykevl
added a commit
that referenced
this issue
Apr 14, 2022
In #2777, a poison value ended up in `runtime.alloc`. This shouldn't happen, especially not for well written code. So I'm not sure why it happens. But here is a fix anyway.
Fix: #2778 |
deadprogram
pushed a commit
that referenced
this issue
Apr 15, 2022
In #2777, a poison value ended up in `runtime.alloc`. This shouldn't happen, especially not for well written code. So I'm not sure why it happens. But here is a fix anyway.
Yes. |
deadprogram
pushed a commit
that referenced
this issue
Apr 16, 2022
In #2777, a poison value ended up in `runtime.alloc`. This shouldn't happen, especially not for well written code. So I'm not sure why it happens. But here is a fix anyway.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following program:
Occasionally triggers a panic in the compiler with stack trace:
The text was updated successfully, but these errors were encountered: