You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
go run -race myprogram -flag1 file1 -flag2 file2 -out outfile -threads 4
and the program starts. It writes the expected things to STDERR but no complain form the race detector.
To test if the race detector was working correctly I ran the example shown here:
and the race detector did show the expected error.
Does this mean that my program does not have a race? Or I cannot see the race detector output because my program is writing to STDERR?
Hi, please ask questions like this on the golang-nuts mailing list.
the issue tracker is for bugs in Go itself and proposals for new
features.
To answer your question, writing to stderr won't interfere with
the race detector. But the race detector can only detect the
race if it actually happens, so you need to run the program
multiple times with various inputs and work loads. (And note
that while the race detector can show races, it can never prove
that the code is free of any data races.)
Hi all,
Sorry for creating a new issue here, but the last one got closed before I could reply.
I have rerun my program using the race detector and there is no complain from the race detector
The text was updated successfully, but these errors were encountered: