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.

Sign up for GitHub

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,cmd/compile: segfaults on loong64 #64134

Open
gopherbot opened this issue Nov 15, 2023 · 9 comments
Open

runtime,cmd/compile: segfaults on loong64 #64134

gopherbot opened this issue Nov 15, 2023 · 9 comments
Labels
arch-loong64 Issues solely affecting the loongson architecture. 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
Unreleased

Comments

@gopherbot
Copy link
Contributor

gopherbot commented Nov 15, 2023 •
edited by bcmills
Loading 

#!watchflakes
post <- goarch == "loong64" && (log ~ `signal: segmentation fault \(core dumped\)` || log ~ `runtime error: invalid memory address or nil pointer dereference`)

Issue created automatically to collect these failures.

Example (log):

signal: segmentation fault (core dumped)

— watchflakes
@gopherbot gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Nov 15, 2023
@gopherbot gopherbot added this to the Unreleased milestone Nov 15, 2023
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "golang.org/x/net/bpf" && test == ""
2023-11-08 19:35 linux-loong64-3a5000 net@fbaf4127 go@e1dc209b x/net/bpf (log) 
signal: segmentation fault (core dumped)

— watchflakes

@bcmills bcmills changed the title x/net/bpf: unrecognized failures runtime,cmd/compile: segfaults on loong64 Nov 15, 2023
@bcmills bcmills added compiler/runtime Issues related to the Go compiler and/or runtime. arch-loong64 Issues solely affecting the loongson architecture. labels Nov 15, 2023
@bcmills bcmills mentioned this issue Nov 15, 2023
Closed
@gopherbot

This comment was marked as resolved.

Sign in to view
This was referenced Nov 15, 2023
Closed
Closed
Closed
Closed
@bcmills
Copy link
Contributor

bcmills commented Nov 15, 2023

(attn @golang/loong64)

This was referenced Nov 15, 2023
Closed
Closed
Closed
Closed
@gopherbot

This comment was marked as resolved.

Sign in to view
This was referenced Nov 15, 2023
Closed
Closed
Closed
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
post <- goarch == "loong64" && (log ~ `signal: segmentation fault \(core dumped\)` || log ~ `runtime error: invalid memory address or nil pointer dereference`)
2023-10-11 14:13 linux-loong64-3a5000 arch@a6bdeed4 go@e1dc209b x/arch/arm/armasm (log) 
signal: segmentation fault (core dumped)
2023-10-11 14:13 linux-loong64-3a5000 arch@a6bdeed4 go@e1dc209b x/arch/arm64/arm64asm (log) 
signal: segmentation fault (core dumped)
2023-10-11 14:13 linux-loong64-3a5000 arch@a6bdeed4 go@e1dc209b x/arch/ppc64/ppc64asm (log) 
signal: segmentation fault (core dumped)
2023-11-13 16:23 linux-loong64-3a5000 sys@11eadc05 go@e1dc209b x/sys/cpu (log) 
signal: segmentation fault (core dumped)
2023-11-13 16:23 linux-loong64-3a5000 sys@11eadc05 go@e1dc209b x/sys/execabs (log) 
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x41 pc=0x1ce7c]

goroutine 1 [running]:
unicode.init()
	/tmp/workdir-host-linux-loong64-3a5000/go/src/unicode/tables.go:9 +0x44
2023-11-13 16:23 linux-loong64-3a5000 sys@11eadc05 go@e1dc209b x/sys/unix (log) 
signal: segmentation fault (core dumped)

— watchflakes

@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
post <- goarch == "loong64" && (log ~ `signal: segmentation fault \(core dumped\)` || log ~ `runtime error: invalid memory address or nil pointer dereference`)
2023-11-08 19:35 linux-loong64-3a5000 net@fbaf4127 go@e1dc209b x/net/bpf (log) 
signal: segmentation fault (core dumped)
2023-11-08 19:35 linux-loong64-3a5000 net@fbaf4127 go@e1dc209b x/net/context (log) 
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x41 pc=0x1cd84]

goroutine 1 [running]:
unicode.init()
	/tmp/workdir-host-linux-loong64-3a5000/go/src/unicode/tables.go:9 +0x44
2023-11-08 19:35 linux-loong64-3a5000 net@fbaf4127 go@e1dc209b x/net/context/ctxhttp (log) 
signal: segmentation fault (core dumped)
2023-11-13 16:23 linux-loong64-3a5000 sys@11eadc05 go@e1dc209b x/sys/cpu (log) 
signal: segmentation fault (core dumped)
2023-11-13 16:23 linux-loong64-3a5000 sys@11eadc05 go@e1dc209b x/sys/execabs (log) 
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x41 pc=0x1ce7c]

goroutine 1 [running]:
unicode.init()
	/tmp/workdir-host-linux-loong64-3a5000/go/src/unicode/tables.go:9 +0x44
2023-11-13 16:23 linux-loong64-3a5000 sys@11eadc05 go@e1dc209b x/sys/unix (log) 
signal: segmentation fault (core dumped)

— watchflakes

@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
post <- goarch == "loong64" && (log ~ `signal: segmentation fault \(core dumped\)` || log ~ `runtime error: invalid memory address or nil pointer dereference`)
2023-10-11 14:13 linux-loong64-3a5000 arch@a6bdeed4 go@e1dc209b x/arch/arm/armasm (log) 
signal: segmentation fault (core dumped)
2023-10-11 14:13 linux-loong64-3a5000 arch@a6bdeed4 go@e1dc209b x/arch/arm64/arm64asm (log) 
signal: segmentation fault (core dumped)
2023-10-11 14:13 linux-loong64-3a5000 arch@a6bdeed4 go@e1dc209b x/arch/ppc64/ppc64asm (log) 
signal: segmentation fault (core dumped)

— watchflakes

@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
post <- goarch == "loong64" && (log ~ `signal: segmentation fault \(core dumped\)` || log ~ `runtime error: invalid memory address or nil pointer dereference`)
2023-10-11 14:13 linux-loong64-3a5000 arch@a6bdeed4 go@e1dc209b x/arch/arm/armasm (log) 
signal: segmentation fault (core dumped)
2023-10-11 14:13 linux-loong64-3a5000 arch@a6bdeed4 go@e1dc209b x/arch/arm64/arm64asm (log) 
signal: segmentation fault (core dumped)
2023-10-11 14:13 linux-loong64-3a5000 arch@a6bdeed4 go@e1dc209b x/arch/ppc64/ppc64asm (log) 
signal: segmentation fault (core dumped)

— watchflakes

@abner-chenc
Copy link
Contributor

I ssh to the Loong64 builder and did these tests, but these errors were not reproduced. I am trying to do more tests to see if I can reproduce the above errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
arch-loong64 Issues solely affecting the loongson architecture. 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.
Projects
Go Compiler / Runtime
Status: Todo
Test Flakes
Status: No status
Milestone
Unreleased
Development

No branches or pull requests
3 participants
@bcmills @gopherbot @abner-chenc