Skip to content
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

os/signal, runtime: fatal signal 33 on android-arm64-corellium due to AllThreadsSyscall rewrite #51213

Closed
prattmic opened this issue Feb 15, 2022 · 3 comments
Assignees
Labels
NeedsInvestigation OS-Android release-blocker
Milestone

Comments

@prattmic
Copy link
Member

@prattmic prattmic commented Feb 15, 2022

android-arm64-corellium failed on https://go.dev/cl/383434. It would seem that signal 33 is fatal on that builder for some reason.

cc @bcmills @aclements

@prattmic prattmic added OS-Android NeedsInvestigation release-blocker labels Feb 15, 2022
@prattmic prattmic self-assigned this Feb 15, 2022
@dmitshur
Copy link
Contributor

@dmitshur dmitshur commented Feb 15, 2022

CC @changkun in case the android-arm64-corellium builder configuration is relevant in this issue.

@dmitshur dmitshur added this to the Go1.18 milestone Feb 15, 2022
@changkun
Copy link
Member

@changkun changkun commented Feb 15, 2022

The current connected (two) android corellium builders should work as expected. These connected builders have no configuration change. Hence if there is a failure, it might likely be a failure due to relevant code change.

@gopherbot
Copy link

@gopherbot gopherbot commented Feb 15, 2022

Change https://go.dev/cl/385954 mentions this issue: runtime: enable sigPerThreadSyscall handling on android

@prattmic prattmic self-assigned this Jun 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation OS-Android release-blocker
Projects
Status: Done
Development

No branches or pull requests

4 participants