-
Notifications
You must be signed in to change notification settings - Fork 18k
x/sync/errgroup: no trace info is shown when nil pointer dereference occurs #73710
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
Labels
BugReport
Issues describing a possible bug in the Go implementation.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
By the way, with 0.14.0, just a panic worked as expected (https://go.dev/play/p/z_TriF0xHr2): package main
import (
"fmt"
"golang.org/x/sync/errgroup"
)
func main() {
var g errgroup.Group
g.Go(func() error {
panic("foo")
})
if err := g.Wait(); err != nil {
fmt.Printf("%#v", err)
}
}
|
11 tasks
This is from #53757 The propagated panic is an |
Thanks report. |
Change https://go.dev/cl/672635 mentions this issue: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
BugReport
Issues describing a possible bug in the Go implementation.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Go version
go version go1.24.3 darwin/arm64
Output of
go env
in your module/workspace:What did you do?
Run this with golang.org/x/sync v0.14.0 (https://go.dev/play/p/MWWuvzsPYXs)
What did you see happen?
and this doesn't tell where this dereference occurs
What did you expect to see?
In v0.13.0 (https://go.dev/play/p/k7rMoNy82F0) there was an info to know that
Related: #53757
The text was updated successfully, but these errors were encountered: