Peter Dillinger 5cb137a860 Work around some new clang-analyze failures (#9515) ... Summary: ... seen only in internal clang-analyze runs after https://github.com/facebook/rocksdb/issues/9481 * Mostly, this works around falsely reported leaks by using std::unique_ptr in some places where clang-analyze was getting confused. (I didn't see any changes in C++17 that could make our Status implementation leak memory.) * Also fixed SetBGError returning address of a stack variable. * Also fixed another false null deref report by adding an assert. Also, use SKIP_LINK=1 to speed up `make analyze` Pull Request resolved: https://github.com/facebook/rocksdb/pull/9515 Test Plan: Was able to reproduce the reported errors locally and verify they're fixed (except SetBGError). Otherwise, existing tests Reviewed By: hx235 Differential Revision: D34054630 Pulled By: pdillinger fbshipit-source-id: 38600ef3da75ddca307dff96b7a1a523c2885c2e		2022-02-07 18:24:36 -08:00
..
folly/folly	Remove using namespace (#9369)	2022-01-12 09:31:12 -08:00
gcc
gtest-1.8.1/fused-src/gtest	Work around some new clang-analyze failures (#9515)	2022-02-07 18:24:36 -08:00