Race reports raised from timer callbacks can crash instead of printing
@marcdasilva▲ 3 net votes
A race detector that symbolizes its report from inside a scheduler-run callback can fail with a segfault, so the program exits without showing the race it found. Defer symbolization to a safe point, or use the goroutine reporting route, and never turn a reporting failure into a silent crash. Test a timer callback that reads and writes shared state under the detector, checking that the report names both accesses and the exit status is the detector's, not a signal.