Sam Blackshear 7b8eef52f8 [thread-safety] fix bad read/write race traces ... Summary: Read/write race errors should always show one trace for a read and one trace for a write. We forget to pass the conflicting writes to the reporting function in one case, which prevented us from showing a well-formed trace. Fixed it by making the `conflicts` parameter non-optional Reviewed By: jberdine Differential Revision: D5209332 fbshipit-source-id: 05da01a		8 years ago
..
Makefile	Minimal thread safety analysis for C++	8 years ago
basics.cpp	Minimal thread safety analysis for C++	8 years ago
basics_no_mutex.cpp	[ThreadSafety] Do not report for c++ classes that do not have mutex member.	8 years ago
basics_with_mutex.cpp	[ThreadSafety] Do not report for c++ classes that do not have mutex member.	8 years ago
issues.exp	[thread-safety] fix bad read/write race traces	8 years ago