runtime: [recovered, repanicked] is displayed for duplicated panics that not recovered.

[fengyoulin]

Go version

go version go1.25.3 linux/amd64

Output of go env in your module/workspace:

GOVERSION='go1.25.3'

What did you do?

package main

var e any = "error message"

func main() {
        defer func() {
                panic(e)
        }()
        panic(e)
}

What did you see happen?

panic: error message [recovered, repanicked]

goroutine 1 [running]:
main.main.func1()
        /home/kylin/work/dupanic.go:7 +0x25
panic({0x475b00?, 0x501ba0?})
        /home/kylin/.golang/go1.25.3/src/runtime/panic.go:783 +0x132
main.main()
        /home/kylin/work/dupanic.go:9 +0x3e

What did you expect to see?

panic: error message

goroutine 1 [running]:
main.main.func1()
        /home/kylin/work/dupanic.go:7 +0x25
panic({0x475b00?, 0x501ba0?})
        /home/kylin/.golang/go1.25.3/src/runtime/panic.go:783 +0x132
main.main()
        /home/kylin/work/dupanic.go:9 +0x3e

[gabyhelp]

Related Issues

• runtime: Go 1.25 panic message changes are not applied universally #73923 (closed)
• testing: panics duplicate information #71517 (closed)
• affected/package: panic.go #60881 (closed)
• spec: clarify when calling recover stops a panic #34530
• runtime: panic message clobbered #30150 (closed)
• runtime: panic while panicking discards error message #52257 (closed)

Related Code Changes

• runtime: don't duplicate reraised panic values in printpanics

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[gopherbot]

Change https://go.dev/cl/716020 mentions this issue: runtime: do not print repanicked when the panic is not recovered