THRIFT: Mutex and ReadWriteMutex leaked memory, now they don't
authorboz <dev-null@apache.org>
Thu, 20 Sep 2007 23:24:16 +0000 (23:24 +0000)
committerboz <dev-null@apache.org>
Thu, 20 Sep 2007 23:24:16 +0000 (23:24 +0000)
commit623096780fa745658e6336390c8e45bfd1f28d24
treebf9bd7b0ccf89b632afccff4b1f69c2b060d4724
parentaa3c5a882c747a7686fc3dac8f7a5572cc55cdfd
THRIFT: Mutex and ReadWriteMutex leaked memory, now they don't

Summary: also added myself to CONTRIBUTORS.

Reviewed By: marc

Test Plan: the following program no longer leaks memory (valgrind):

int main(int argc, char **argv){
  Mutex mu;
  mu.lock();
  mu.unlock();
}

Revert Plan: ok

Notes: this is kind of important

git-svn-id: https://svn.apache.org/repos/asf/incubator/thrift/trunk@665279 13f79535-47bb-0310-9956-ffa450edef68
CONTRIBUTORS
lib/cpp/src/concurrency/Mutex.cpp
lib/cpp/src/concurrency/Mutex.h