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

syscall: TestExec failures with SIGSEGV on riscv64 #64791

Open
gopherbot opened this issue Dec 18, 2023 · 4 comments
Open

syscall: TestExec failures with SIGSEGV on riscv64 #64791

gopherbot opened this issue Dec 18, 2023 · 4 comments
Labels
arch-riscv Issues solely affecting the riscv64 architecture. compiler/runtime Issues related to the Go compiler and/or runtime. help wanted NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@gopherbot
Copy link
Contributor

gopherbot commented Dec 18, 2023

#!watchflakes
post <- goarch == "riscv64" && pkg == "syscall" && test == "TestExec" && `signal: segmentation fault`

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestExec (1.19s)
    exec_unix_test.go:317: 
        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 Dec 18, 2023
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "syscall" && test == "TestExec"
2023-12-18 19:42 linux-riscv64-unmatched go@08bec0db syscall.TestExec (log)
--- FAIL: TestExec (1.19s)
    exec_unix_test.go:317: 
        signal: segmentation fault (core dumped)

watchflakes

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Dec 18, 2023
@bcmills bcmills added the arch-riscv Issues solely affecting the riscv64 architecture. label Jan 2, 2024
@bcmills bcmills changed the title syscall: TestExec failures syscall: TestExec failures with SIGSEGV on riscv64 Jan 2, 2024
@bcmills
Copy link
Contributor

bcmills commented Jan 2, 2024

(attn @golang/riscv64)

@bcmills
Copy link
Contributor

bcmills commented Jan 2, 2024

Note that this is the regression test added for #41702.

@bcmills bcmills added this to the Backlog milestone Jan 2, 2024
@mengzhuo
Copy link
Contributor

mengzhuo commented Jan 9, 2024

I can reproduce this issue on visionfive2 at master

=== RUN   TestExec
runtime: g639: frame.sp=0x3f54037fe0 top=0x3f54037fd8
        stack=[0x3f54037800-0x3f54038000
fatal error: traceback did not unwind completely
runtime: g640: frame.sp=0x3f5425cfe0 top=0x3f5425cfd8
        stack=[0x3f5425c800-0x3f5425d000
fatal error: traceback did not unwind completely
runtime: g611: frame.sp=0x3f542597e0 top=0x3f542597d8
        stack=[0x3f54259000-0x3f54259800
fatal error: traceback did not unwind completely

runtime stack:
runtime.throw({0x19d675?, 0x3fcb6f97c0?})
        /root/godev/src/runtime/panic.go:1023 +0x44 fp=0x3fcb6f9638 sp=0x3fcb6f9610 pc=0x46f44
runtime.(*unwinder).finishInternal(0x3fcb6f9738?)
        /root/godev/src/runtime/traceback.go:565 +0x118 fp=0x3fcb6f9670 sp=0x3fcb6f9638 pc=0x71b38
runtime.(*unwinder).next(0x3fcb6f9738?)
        /root/godev/src/runtime/traceback.go:446 +0x2a0 fp=0x3fcb6f96f0 sp=0x3fcb6f9670 pc=0x71990
runtime.scanstack(0x3f5418a380, 0x3f54029268)
        /root/godev/src/runtime/mgcmark.go:899 +0x25c fp=0x3fcb6f9818 sp=0x3fcb6f96f0 pc=0x2df9c
runtime.markroot.func1()
        /root/godev/src/runtime/mgcmark.go:241 +0xc8 fp=0x3fcb6f9868 sp=0x3fcb6f9818 pc=0x2cbe0
runtime.markroot(0x3f54029268, 0x1c, 0x1)
        /root/godev/src/runtime/mgcmark.go:215 +0x1e0 fp=0x3fcb6f98f0 sp=0x3fcb6f9868 pc=0x2c8e8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-riscv Issues solely affecting the riscv64 architecture. compiler/runtime Issues related to the Go compiler and/or runtime. help wanted NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Status: No status
Development

No branches or pull requests

4 participants