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

segmentation error when using sync.Map.Load() #40865

Closed
TUTUBIG opened this issue Aug 18, 2020 · 4 comments
Closed

segmentation error when using sync.Map.Load() #40865

TUTUBIG opened this issue Aug 18, 2020 · 4 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
Backlog

Comments

@TUTUBIG
Copy link

TUTUBIG commented Aug 18, 2020 •
edited by randall77 

unexpected fault address 0x0 fatal error: fault [signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0x45a81f]
goroutine 16 [running]:
runtime.throw(0xec2328, 0x5)
   /usr/local/go/src/runtime/panic.go:774 +0x72 fp=0xc001321c98 sp=0xc001321c68 pc=0x42da32 
runtime.sigpanic()
   /usr/local/go/src/runtime/signal_unix.go:401 +0x3de fp=0xc001321cc8 sp=0xc001321c98 pc=0x44250e 
aeshashbody()
   /usr/local/go/src/runtime/asm_amd64.s:1143 +0x38f fp=0xc001321cd0 sp=0xc001321cc8 pc=0x45a81f 
runtime.nilinterhash(0xc001321dc0, 0x0, 0x0)
   /usr/local/go/src/runtime/alg.go:171 +0xb5 fp=0xc001321d18 sp=0xc001321cd0 pc=0x403325 
runtime.mapaccess2(0xd72f00, 0x0, 0xc001321dc0, 0x10, 0xdc5040)
   /usr/local/go/src/runtime/map.go:465 +0x25d fp=0xc001321d60 sp=0xc001321d18 pc=0x40dc4d 
sync.(*Map).Load(0xc0003a3d70, 0xd3d5c0, 0xc001321ed8, 0xc001a3f680, 0xc001a19dd0, 0x1) 
  /usr/local/go/src/sync/map.go:104 +0xa9 fp=0xc001321de0 sp=0xc001321d60 pc=0x4676d9

what this reason should be？
@TUTUBIG
Copy link
Author

TUTUBIG commented Aug 18, 2020

go 1.14 running in Docker container

@randall77
Copy link
Contributor

A fault at runtime/asm_amd64.s:1143 seems impossible. The instruction there:

	AESENC	X2, X2

can't fault.

Are you sure it is go 1.14? I also checked 1.14.1 and 1.14.2, same deal.

@networkimprov
Copy link

@TUTUBIG please fill in the issue template from https://github.com/golang/go/issues/new/choose

It's really difficult to diagnose problems with incomplete information.

Please provide a complete program to reproduce the problem if possible.

@dmitshur dmitshur added 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. labels Aug 18, 2020
@dmitshur dmitshur added this to the Backlog milestone Aug 18, 2020
@TUTUBIG
Copy link
Author

TUTUBIG commented Aug 21, 2020

i'll close this issue now and maybe reopen it if this problem come out again

@TUTUBIG TUTUBIG closed this as completed Aug 21, 2020
@golang golang locked and limited conversation to collaborators Aug 21, 2021
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
Backlog
Development

No branches or pull requests
5 participants
@networkimprov @dmitshur @randall77 @gopherbot @TUTUBIG