-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: race detector mis-identifies runtime.racereadrange()
as the read location
#51459
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
Comments
It seems related to #51247, could you reproduce this issue on master? |
@mengzhuo I can reproduce this issue on master. $ gotip version
go version devel go1.19-46afa89 Fri Mar 4 15:48:03 2022 +0000 darwin/amd64 I can also reproduce it on linux/amd64. |
Change https://go.dev/cl/393154 mentions this issue: |
Some additional info if this wasn't known:
Not only does I built from https://go.dev/cl/393154 and now it shows as:
|
I can reproduce it with |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes: go1.18rc1
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Ran tests with
go test -race
.What did you expect to see?
The data race warnings printed list the locations in user code of both the racing read and write in all cases.
What did you see instead?
The read location of a
time.Time
value is identified in the stack trace asruntime.racereadrange()
.In contrast, the race output from `TestNarrowValue` correctly identifies the read and write locations in user code
The text was updated successfully, but these errors were encountered: