[FIX] gProbeDepth modification when child thread running

Now gProbeDepth variable is changed only if thread API tracing is
activated

Change-Id: Id495d5bfcfd92f2f12acf563162ae53850e3696a
Signed-off-by: Alexander Aksenov <a.aksenov@samsung.com>

diff --git a/probe_tizenapi/tizen_thread.cpp b/probe_tizenapi/tizen_thread.cpp
index cd45b8e..b332012 100755 (executable)
--- a/probe_tizenapi/tizen_thread.cpp
+++ b/probe_tizenapi/tizen_thread.cpp
@@ -168,13 +168,13 @@ _ThreadImpl::ThreadProc(void* params) {
                FLUSH_LOCAL_BUF();
 
                preBlockEnd();
+               probingEnd();
        }
        // all probe should be reachable inside thread start_routine (user implemented Thread::Run)
-       probingEnd();
        (ThreadProcp)(params);
-       probingStart();
        //
        if (postBlockBegin(blockresult)) {
+               probingStart();
                setProbePoint(&probeInfo);
 
                _ThreadImpl* pSelf =(_ThreadImpl*)params;