readme updated

diff --git a/README.md b/README.md
index 1ac5da576565ea6690ae012b4f21044a866c2d54..e7a2a074531370b84e485c76f07bd07009df67e7 100644 (file)
--- a/README.md
+++ b/README.md
@@ -62,13 +62,13 @@ In the following examples option `-c` is used to specify path to the GBS config
 #### Build for ARM Tizen TM1 target
 
 ```console
-~/heaptrack$ gbs -c ../gbs-config/gbs.conf build -P profile.arm.snapshot -A armv7l
+~/heaptrack$ gbs -c docs/gbs-config/gbs.conf build -P profile.arm.snapshot -A armv7l
 ```
 
 #### Build for x86 Tizen emulator
 
 ```console
-~/heaptrack$ gbs -c ../gbs-config/gbs.conf build -P profile.emul32.snapshot -A i586
+~/heaptrack$ gbs -c docs/gbs-config/gbs.conf build -P profile.emul32.snapshot -A i586
 ```
 
 ### Building GUI
@@ -115,29 +115,33 @@ Basic instructions for Running the Memory Profiler under  Visual Studio are prov
      ![Run Memory Profiler](docs/image/run_memory_profiler.png)
 
 
-   * If no Tizen device is connected and no Tizen emulators are running then Emulator Manager will be started. Please launch the type of emulator you want to use for running and profiling your application.
+   * If no Tizen device is connected and no Tizen emulators are running then Emulator Manager will be started. Please launch the type of emulator you want to use for running and profiling your application. 
 
      ![Launch Emulator](docs/image/start_emulator.png)
 
-
-   * If everything is OK then the application starts as if you run it normally (using Start Debugging in Visual Studio).
+   
+   * If everything is OK then the application starts as if you run it normally (using Start Debugging in Visual Studio). 
 
      ![Tizen application running](docs/image/memory_profiling_app_started.png)
 
 
-   * In case of errors the Output Window will display them (the output below corresponds to the normal operation case).
+   * Output Window will display any information messages (debug, warnings, etc). 
 
      ![Memory Profiler Output Window](docs/image/memory_profiling_msvs_output.png)
 
 
-   * After finishing the application the memory profiling data file will be copied from Tizen to Windows host.
+   * After finishing the application the memory profiling data will be displayed with the GUI application (for closing application you may press "Home" or "Back" keys). 
+
+     ![Close Application](docs/image/close_application.png)
+
+
+   * Also you can display any previous debug session with Session Explorer (In the menu, Tools > Tizen > Profiler > Session Explorer).
 
-### Step 2. Running Memory Profiler GUI
-   * You can open the memory profiling data file in the GUI application to analyze it. In the menu, choose Tools > Tizen > Profiler > Show Memory Profiler.
+     ![Open Session Explorer](docs/image/open_session_explorer.png)
 
-     ![Run Memory Profiler GUI](docs/image/run_memory_profiler_gui.png)
+     ![Open Session Explorer](docs/image/session_explorer_memory_profiler.png)
 
-### Step 3. Analyzing the results
+### Step 2. Analyzing the results
    * The GUI application provides several views to the memory profiling data. The views include:
 
        - summary page with information on which process was profiled, its total runtime, some memory related statistics, etc.
@@ -150,7 +154,7 @@ Basic instructions for Running the Memory Profiler under  Visual Studio are prov
        - number of instances over time graph
        - number of memory allocations over time graph
        - size of memory allocated over time graph
-       - allocation histogram displaying the number of allocations (the total number and the several topmost code locations) belonging to one of the groups divided by allocation size (0 - 8 bytes, 9 - 16 bytes, ... , 512 bytes - 1 KB, more than 1 KB)
+       - allocation histogram displaying the number of allocations (the total number and the several topmost code locations) belonging to one of the groups divided by allocation size (0 - 8 bytes, 9 - 16 bytes, docs. , 512 bytes - 1 KB, more than 1 KB)
 
 #### Managed heap view sample
 

diff --git a/docs/image/close_application.png b/docs/image/close_application.png
new file mode 100644 (file)
index 0000000..024f689
Binary files /dev/null and b/docs/image/close_application.png differ

diff --git a/docs/image/memory_profiling_app_started.png b/docs/image/memory_profiling_app_started.png
index ff42d1a6bc3cb056ecf9943976c6151a515ca590..49becb224fc3ad7aad04b3446821d16cbcfd509c 100644 (file)
Binary files a/docs/image/memory_profiling_app_started.png and b/docs/image/memory_profiling_app_started.png differ

diff --git a/docs/image/memory_profiling_msvs_output.png b/docs/image/memory_profiling_msvs_output.png
index 6f4ae7b07faa2df6d28d66dcd9df5f0f132f6b5a..13d85bf827170c54dca1c71aa67f2add76c52011 100644 (file)
Binary files a/docs/image/memory_profiling_msvs_output.png and b/docs/image/memory_profiling_msvs_output.png differ

diff --git a/docs/image/open_session_explorer.png b/docs/image/open_session_explorer.png
new file mode 100644 (file)
index 0000000..7733d70
Binary files /dev/null and b/docs/image/open_session_explorer.png differ

diff --git a/docs/image/run_memory_profiler.png b/docs/image/run_memory_profiler.png
index 0d7208dfece6817e1db32069b2588555d4d847e0..5b56feb3a22bd516404a46f94628d15c28401ad2 100644 (file)
Binary files a/docs/image/run_memory_profiler.png and b/docs/image/run_memory_profiler.png differ

diff --git a/docs/image/session_explorer_memory_profiler.png b/docs/image/session_explorer_memory_profiler.png
new file mode 100644 (file)
index 0000000..99527ae
Binary files /dev/null and b/docs/image/session_explorer_memory_profiler.png differ

diff --git a/docs/image/start_emulator.png b/docs/image/start_emulator.png
index 5d09774119e0174d412c7c4c28354c47e0dd2578..c4e1a794009086f95e1e628e31c1b5d9e9ea4a0c 100644 (file)
Binary files a/docs/image/start_emulator.png and b/docs/image/start_emulator.png differ