-
Notifications
You must be signed in to change notification settings - Fork 18k
os/exec: fatal error: runtime·unlock: lock count #30594
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
Comments
I can't seem to reproduce your problem. I can do
Then run the resulting binary on an arm builder just fine. Why are you building with Maybe something about running arm binaries on your arm64 chip is broken? Atomics not working correctly, perhaps? |
@randall77 |
#28431 was fixed in 1.12 (and that fix was backported to 1.11.4), so you should be able to run arm64 binaries just fine. Actually, that fix was just for GOOS=android, but you use GOOS=linux. It looks like you're running on android, though. Maybe try GOOS=android (for both arm and arm64) to see if that fixes it? |
@randall77 it is running on Sony SO-01L not fine, except for another android phone. I changed
|
Ok, so you are using GOOS=android, GOARCH=arm64.
Could you elaborate? Did you try it on multiple devices? What was the difference in behavior? What is the difference between the devices? |
sony -> runs for a while and then throws an exception if I delete the code of os/exec, both of them run infinite loop and no exception. I think there is a problem at |
It's not at all clear to me what platform this issue is supposed to be against. The original report was on If this is still a problem, I suggest that you file a new issue (with fresh answers for the questions in the issue template). |
What version of Go are you using (
go version
)?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?
build the code on Mac:
~CGO_ENABLED=0 GOOS=linux GOARCH=arm go build
run the code at android phone(sony SO-01L aos9)
err.log
What did you expect to see?
The problem is similar like #29173.
How can it be solved?
The text was updated successfully, but these errors were encountered: