5 Commits (03703e316c11b48718d4f4430f49842588b0935a)

Author	SHA1	Message	Date
Daiva Naudziuniene	5938c6331d	[ThreadSafety] Extending lock model with lock_quard. ... Reviewed By: jberdine Differential Revision: D5217177 fbshipit-source-id: b7992a0	8 years ago
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
Daiva Naudziuniene	093a00af9b	[ThreadSafety] Do not report for c++ classes that do not have mutex member. ... Reviewed By: jberdine Differential Revision: D5182255 fbshipit-source-id: f954337	8 years ago
Daiva Naudziuniene	f4b9bb3e3b	[ThreadSafety] Do not report unprotected writes for c++. ... Reviewed By: jberdine Differential Revision: D5172030 fbshipit-source-id: 945acba	8 years ago
Josh Berdine	bf504c5b70	Minimal thread safety analysis for C++ ... Summary: This is a minimal change to (poorly) recognize and model std::mutex lock and unlock methods, and to surface all thread safety issues for C++ based on the computed summaries with no filtering. This ignores much of the Java analysis, including everything about the Threads domain. The S/N is comically low at this point. Reviewed By: sblackshear Differential Revision: D5120485 fbshipit-source-id: 0f08caa	8 years ago