-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
x/mobile: seccomp prevented call to disallowed arm64 system call 434 #70508
Comments
#70495 |
CC @kolyshkin Is this being built with |
This is the build command we use in ci:
This is the local one:
We've tested both ways. It doesn't work either
These AAR-packaged native libraries are used later through JNI interaction in this android open-source project. |
I see that two solutions were introduced for this problem:
The second solution was preferred and eventually merged into version 1.23.3. I don’t understand the reasoning behind this choice because, as far as I know, most people use Go to write libraries, not fully native apps on Android. And Go’s internal OS signal handling does not work when compiling a shared library via gomobile. |
Workaround on the Android side if you don’t want to downgrade the Go version: |
The discussion on https://go.dev/cl/610515 explains why we went with the That said, I think we can change the |
Go version
go version 1.22.9 darwin/arm64
Output of
go env
in your module/workspace:What did you do?
I am attempting to build our project library for the Android team using Go 1.23.3.
You can refer to revert of the changes here: Pull Request #1856.
What did you see happen?
I've noticed crashes when running on Android versions below 12.
It seems this issue should be resolved here.
9563300
https://gpages.juszkiewicz.com.pl/syscalls-table/syscalls.html
434 - seems https://www.man7.org/linux/man-pages/man2/pidfd_open.2.html
Android log
What did you expect to see?
When I use Go 1.22.9, everything works as expected (see the PR above).
TL;DR: The fix for the incorrect syscall in Go 1.23.3 doesn't seem to work.
The text was updated successfully, but these errors were encountered: