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
runtime: Breakpoint SIGSEGV on ppc64le #52101
Labels
Milestone
Comments
alexsaezm
added a commit
to alexsaezm/go
that referenced
this issue
Apr 1, 2022
Currently runtime.Breakpoint generates a SIGSEGV in ppc64. The solution is an unconditional trap similar to what clang and gcc do. It is documented in the section C.6 of the ABI Book 3. Fixes golang#52101
Change https://go.dev/cl/397554 mentions this issue: |
alexsaezm
added a commit
to alexsaezm/go
that referenced
this issue
Apr 1, 2022
Currently runtime.Breakpoint generates a SIGSEGV in ppc64. The solution is an unconditional trap similar to what clang and gcc do. It is documented in the section C.6 of the ABI Book 3. Fixes golang#52101
alexsaezm
added a commit
to alexsaezm/go
that referenced
this issue
Apr 1, 2022
Currently runtime.Breakpoint generates a SIGSEGV in ppc64. The solution is an unconditional trap similar to what clang and gcc do. It is documented in the section C.6 of the ABI Book 3. Fixes golang#52101
alexsaezm
added a commit
to alexsaezm/go
that referenced
this issue
May 23, 2022
Currently runtime.Breakpoint generates a SIGSEGV in ppc64. The solution is an unconditional trap similar to what clang and gcc do. It is documented in the section C.6 of the ABI Book 3. Fixes golang#52101
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What version of Go are you using (
go version
)?Also happens in all versions.
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
In ppc64le, if you run the following code:
you get a SIGSEGV:
What did you expect to see?
A trap like in amd64.
What did you see instead?
a SIGSEGV.
The text was updated successfully, but these errors were encountered: