fix the itc crash 35/108235/3 accepted/tizen_3.0.m2_mobile accepted/tizen_3.0.m2_tv accepted/tizen_3.0.m2_wearable tizen_3.0.m2 accepted/tizen/3.0.m2/mobile/20170104.125301 accepted/tizen/3.0.m2/tv/20170104.125613 accepted/tizen/3.0.m2/wearable/20170104.125819 accepted/tizen/3.0/common/20170103.173107 accepted/tizen/3.0/ivi/20170103.160317 accepted/tizen/3.0/mobile/20170103.160222 accepted/tizen/3.0/tv/20170103.160239 accepted/tizen/3.0/wearable/20170103.160257 submit/tizen_3.0.m2/20170104.093750 submit/tizen_3.0/20170103.123536
authorJooseok Park <jooseok.park@samsung.com>
Tue, 3 Jan 2017 11:42:03 +0000 (20:42 +0900)
committerJooseok Park <jooseok.park@samsung.com>
Tue, 3 Jan 2017 11:49:20 +0000 (20:49 +0900)
 - TC: ITc_iotcon_remote_resource_get_cached_representation_p
 - Although find callback is removed, sometimes callback is called
 - it is caused by timing issue
 - So, need to double-check callback pointer

Change-Id: I0f6e95cd527cac349f04bc47d29cdee021c268f5

packaging/iotcon.spec
src/ic-ioty-ocprocess.c

index 42be1a5..38aa22a 100644 (file)
@@ -1,6 +1,6 @@
 Name:       iotcon
 Summary:    Tizen IoT Connectivity
-Version:    0.3.9
+Version:    0.3.10
 Release:    0
 Group:      Network & Connectivity/Service
 License:    Apache-2.0
index 2e1fe46..e1f8ce2 100644 (file)
@@ -141,6 +141,10 @@ static gboolean _icl_ioty_ocprocess_find_idle_cb(gpointer p)
                        resource = resource_list->data;
                        resource->is_found = true;
                        cb = (iotcon_found_resource_cb)cb_data->cb;
+                       if (NULL == cb) {
+                               WARN("It is already stopped");
+                               return G_SOURCE_REMOVE;
+                       }
                        INFO("Call the callback");
                        if (IOTCON_FUNC_STOP == cb(resource, IOTCON_ERROR_NONE, cb_data->user_data)) {
                                /* Stop */