Update README.md

diff --git a/README.md b/README.md
index 4d94e22..dfd5c1a 100644 (file)
--- a/README.md
+++ b/README.md
@@ -30,6 +30,8 @@ For unpacking on Windows, please see [the details](docs/DETAILED.md#download-and
 
 [[SHA256 values for archive contents]](#checksums)
 
+You can also build and run the profiler entirely in Docker. For instructions, please see [Docker Instructions](#docker-instructions)
+
 ### Initialization of device for measurements [[Details]](docs/DETAILED.md#prepare-tizen-device-for-measurements)
 
 2\. Put Tizen RPMs to VM's /home/ubuntu/device-rpms for:
@@ -110,6 +112,17 @@ Next several views are graphs for different memory consumption statistics (also,
 Here, the "consumed" is used instead of "leaks", which is more precise.
 The "consumed" view shows memory consumption graph for top memory consuming function (separately, as shown in color, and also total consumption - the topmost graph).
 
+
+
+## Docker Instructions
+
+1. When building in Docker, first thing you need to do is to create a `coreclr-devel` directory and put coreclr-devel rpms for the CoreCLR versions you use on your devices in this folder. You can find out which version of CoreCLR is installed on your device using `rpm -qa` command. Alternatively, you can let docker download the latest `coreclr-devel` package from download.tizen.org. If you choose this option, leave the `coreclr-devel` folder empty and proceed to step 2, but please make sure that the device also has the latest coreclr package installed.
+2. Run 
+```
+./scripts/docker/heaptrack.sh org.tizen.example.HelloWorld.Tizen /opt/usr/home/owner/apps_rw/HelloWorld.Tizen/bin/HelloWorld.Tizen.exe
+```
+to build the profiler and launch profiling of HelloWorld application. The rest of the steps are the same as in the Measurements section of this document.
+
 ## Troubleshooting
 
 1\. The heaptrack is built for one of latest Tizen Unified TM1 system.

diff --git a/scripts/docker/heaptrack-run.sh b/scripts/docker/heaptrack-run.sh
index 7839e5f..80646d6 100755 (executable)
--- a/scripts/docker/heaptrack-run.sh
+++ b/scripts/docker/heaptrack-run.sh
@@ -44,7 +44,7 @@ fi
 $SDB push $HEAPTRACK_DATA_DIR/$DEVICE_ARCH/bin/* $DEVICE_HEAPTRACK_PATH/build/bin/ &>/dev/null
 $SDB push $HEAPTRACK_DATA_DIR/$DEVICE_ARCH/lib/heaptrack/*.so $DEVICE_HEAPTRACK_PATH/build/lib/heaptrack/ &>/dev/null
 $SDB push $HEAPTRACK_DATA_DIR/$DEVICE_ARCH/lib/heaptrack/libexec/* $DEVICE_HEAPTRACK_PATH/build/lib/heaptrack/libexec/ &>/dev/null
-$SDB push $HEAPTRACK_DATA_DIR/$DEVICE_ARCH/libprofiler.so $DEVICE_HEAPTRACK_PATH/build/bin/ &>/dev/null
+$SDB push $HEAPTRACK_DATA_DIR/$DEVICE_ARCH/$CORECLR_VERSION/libprofiler.so $DEVICE_HEAPTRACK_PATH/build/bin/ &>/dev/null
 $SDB push $SCRIPTS_PATH/../* $DEVICE_HEAPTRACK_PATH/build/bin/ &>/dev/null
 $SDB shell "cd $DEVICE_HEAPTRACK_PATH/build/bin
             ./heaptrack-pid.sh $DEVICE_HEAPTRACK_PATH/build/bin $DEVICE_HEAPTRACK_PATH/build/bin/res.gz ${APP_ID} ${APP_PATH}"