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

Jump to bottom

runtime: unexpected fault address 0x0 from inside assertI2I2 #20901

Closed
whyrusleeping opened this issue Jul 4, 2017 · 5 comments
Closed

runtime: unexpected fault address 0x0 from inside assertI2I2 #20901

whyrusleeping opened this issue Jul 4, 2017 · 5 comments
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone
Go1.10

Comments

@whyrusleeping
Copy link

whyrusleeping commented Jul 4, 2017 •
edited

What version of Go are you using (go version)?

go version go1.8.3 linux/amd64

What operating system and processor architecture are you using (go env)?

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/whyrusleeping/gopkg"
GORACE=""
GOROOT="/home/whyrusleeping/go"
GOTOOLDIR="/home/whyrusleeping/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build194663187=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"

What did you do?

Was running a go program and it crashed with this stack trace: https://gist.github.com/whyrusleeping/680bb5d41a762eac6a48cf5b4ea99e66

What did you expect to see?

I'm fine if my code panics, but generally seeing 'fault' in a stack trace makes me think that its a go issue.

Its worth noting that i was experimenting with plugins. the plugins were working great, and plugin code was not being run when the crash happened.

ref: ipfs/kubo#4031
@ianlancetaylor ianlancetaylor changed the title unexpected fault address 0x0 from inside assertI2I2 runtime: unexpected fault address 0x0 from inside assertI2I2 Jul 4, 2017
@ianlancetaylor
Copy link
Contributor

I agree that this should not happen.

Is this repeatable at all?

@ianlancetaylor ianlancetaylor added this to the Go1.10 milestone Jul 4, 2017
@whyrusleeping
Copy link
Author

I havent been able to reproduce this again, but i can try. Anything in particular i should try and gather to help debug?

@bradfitz bradfitz added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jul 5, 2017
@aclements
Copy link
Member

@whyrusleeping, any luck reproducing this?

Looking at the code, I don't see how could possibly happen. The only dereference on this line is of m, and we just checked if m was nil.

It's worth noting that this code has been completely rewritten for 1.10, so even we if do track this down in 1.8 (or 1.9), it likely doesn't apply to 1.10.

@aclements aclements added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Nov 8, 2017
@whyrusleeping
Copy link
Author

@aclements I havent been able to. My only hint was that I was using plugins at the time, and maybe even replacing the file of a plugin that was in use.

@aclements
Copy link
Member

Thanks for the quick reply. I'm going to go ahead and close this as unreproducible.

@golang golang locked and limited conversation to collaborators Nov 9, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Milestone
Go1.10
Development

No branches or pull requests
5 participants
@bradfitz @whyrusleeping @aclements @ianlancetaylor @gopherbot