Fixing unzClose and unzCloseCurrent not guarded 92/45092/2 accepted/tizen/mobile/20150804.000145 accepted/tizen/tv/20150804.000155 accepted/tizen/wearable/20150804.000207 submit/tizen/20150803.232230
authorPawel Sikorski <p.sikorski@samsung.com>
Thu, 30 Jul 2015 10:15:52 +0000 (12:15 +0200)
committerPawel Sikorski <p.sikorski@samsung.com>
Mon, 3 Aug 2015 14:26:15 +0000 (07:26 -0700)
commitb42db4ea2f31b2ba84ba4e4c69749fcaef5d7378
tree3367d33225e31c700e3fa3c8fdec977930bbd858
parent0f4d4af31b7dc6c5918843bbd37d16a95f1b45f4
Fixing unzClose and unzCloseCurrent not guarded

During unzipping, unzClose and unzCloseCurrent is not called
in all possible conditions.

Solution: introducing class that will guard it.

Note: in original implementation, in case of successful unzOpenCurrent
and unzReadCurrentFile, there was no unzCloseCurrent (next call was
to unzGoToNext).
In this implementation, unzCloseCurrent is called.

Change-Id: Idaf883618922177b5ebdf1ae5026ce3db9eaaaa2
src/common/utils/file_util.cc