diff options
| author | Mark Salyzyn <salyzyn@google.com> | 2016-03-01 14:59:32 -0800 |
|---|---|---|
| committer | Mark Salyzyn <salyzyn@google.com> | 2016-03-02 11:37:21 -0800 |
| commit | c3484161980cdea915c893a233f54b14a75d151f (patch) | |
| tree | 1c7b10e205efa8b2375fd82b4eabaee7fec9e621 /libunwindstack/tests/MemoryLocalTest.cpp | |
| parent | 539a79e5295e83ab1070de6082988f6b5fe7eae0 (diff) | |
logd: clarify release_Locked() for static analyzer
(cherry pick from commit 0ecdec7a0922f5e99569c558fd3c6440b826e583)
release_Locked() is called with a reference count and threadRunning,
the static analyzer can not tell this and estimates that a call to
delete this will occur. So let us invent a new call
release_nodelete_Locked() to ensure it is clear we will not be
arranging a delete this in the context of this code path. The
delete this will follow in the immediate codepath in this function
after threadRunning is cleared, and decRef_Locked() is called.
Change will also remove any developer FUD regarding release_Locked()
usage at this location.
SideEffects: None
Bug: 27434831
Change-Id: I91b060b2dadc72cc449fa381c934afb577bee037
Diffstat (limited to 'libunwindstack/tests/MemoryLocalTest.cpp')
0 files changed, 0 insertions, 0 deletions