MB-16357: Create a variable to get correct locking scope 76/56976/2
authorJim Walker <jim@couchbase.com>
Thu, 12 Nov 2015 12:04:56 +0000 (12:04 +0000)
committerChiyoung Seo <chiyoung@couchbase.com>
Thu, 12 Nov 2015 16:36:54 +0000 (16:36 +0000)
commit8a2b7511c7d858c459dfbbcc25ca2186949bb8b8
tree17bd3f34d9e19b1949a29fca27a64da9a24c1031
parent8939f8336f5b057b4af09e43c39c437455c62364
MB-16357: Create a variable to get correct locking scope

A mistake in 495e00acc24 means that no variable is
created for the ReaderLockHolder, the compiler either
optimises away the lock constructor/destructor or the lock
scope is wrong.

Either way we need to create a variable.

Change-Id: I642ac64d71b73d3d78207ff50d33539a06ce0e7e
Reviewed-on: http://review.couchbase.org/56976
Tested-by: buildbot <build@couchbase.com>
Reviewed-by: Dave Rigby <daver@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
src/ep.cc