runtime: unexpected signal on Termux android/arm64 #29623
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
odeke-em
changed the title
odeke-em
added
the
NeedsInvestigation
|
Thank you for filing this bug @uudashr and welcome to the Go project! I'll kindly page some experts @ianlancetaylor @randall77 @eliasnaur |
|
This looks like a nil mspan pointer in the span list. |
|
It's easy to crash on android/arm when run test... Might happen on other command also. I'll post new findings |
|
I try to do another test using the same source code.. 1x hung 1x show 1x error on increased allocation count 1x fatal error: unexpected signal during runtime execution |
|
Could you try with 1.12beta2 and see if the crash persists ? |
|
Cannot try.. still fail install on Termux. No binary for Android and manual build still failed |
|
Ah I didn't realize there were no beta builds for android. Could you try setting |
|
No luck The location of go binary is and the GOROOT |
|
Oh I see. Your distribution is a bit different. The standard layout is - $GOROOT/bin/go --> binary The standard release tarball unzips them into this structure. I believe if you put your go 1.11.4 in such a structure, then it should work. Sorry, looks like you have to do some more work here. |
|
@agnivade thanks... I follow your suggestion and made symlink on the $GOROOT/bin, we have progress but still fail Another attempt show different output |
|
This looks like a code issue. Perhaps others on this thread can clarify. |
|
I failed to reproduce the error on my Google Pixel device. I installed Termux, ran
for more than a hundred iterations. They all succeeded. |
|
@eliasnaur could you confirm the |
|
Same as yours, |
|
Hmm.. I just reinstall my termux and fail to run test on first attempt. That was weird. |
|
@eliasnaur could you share your |
|
|
I'm clueless. Others might have clue on this? |
|
Can you run androidtest.bash from a host machine on your device successfully? See the readme in the misc/android directory for instructions. You'll need to set CC_FOR_TARGET to an ndk clang. |
|
Exec Attempt 1 Attempt 2 Attempt 3 Attempt 4 Attempt 5 Attempt 6 |
|
Thanks. I meant for you to try running Go 1.12b2 androidtest.bash from a host machine (Linux/macOS/Windows) connected to your Android device. Use GOARCH=arm64 to select arm64 and set CC_FOR_TARGET to an NDK standalone toolchain. You'll also need to point GOROOT_BOOTSTRAP to another Go installation on your host. |
|
Android version: 8.1.0 Run the test: Output |
|
Thank you. All tests passed with 1.12b2. Can you try the same with 1.11.4 (from source)? If that doesn't fail either, I'm not sure what to do next. Perhaps try and build 1.12 on your host to run on the device. Termux is open source, right? If so it should contain build instructions. |
|
Surprise.. 1.11.4 doesn't fail Output@eliasnaur thanks btw |
|
Great to see a lot of movement here, how's it going @uudashr and @eliasnaur? Shall we punt this to Go1.13? I ask because we are at the very end of the Go1.12 development/fixing cycle. |
|
I can't reproduce the problem so I can't move this further. Go 1.13 is fine for me. |
|
Roger that, thanks @eliasnaur for the confirmation! |
gopherbot
added
the
compiler/runtime
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 envOutputWhat did you do?
I create project outside the gopath using go mod
and have this files
doc.goandhello_test.gothen run test
What did you expect to see?
Always shows
What did you see instead?
1 out of 10 stuck/hung
and
1 out of 10 shows
The text was updated successfully, but these errors were encountered: