[CONPRO-1212] Removing invocation of lock_guard destructor.
std::lock_guard follows RAII for std::mutex. Invoking
std::lock_guard<std::mutex>::~lock_guard() makes unlock
call twice on underlying mutex. As per the API documentation
calling unlock from thread which does not own lock results in
undefined behaviour.
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/243
(cherry picked from commit
fc681e089d3bbbbd16f90ad05d53208f9a1602d1)
Change-Id: Iaf21d318f5fa46daf2bcc17f0f07ffe9aa887b9d
Signed-off-by: Harry <h.marappa@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>