Code autogenerated from Kurento/doc-kurento@7e13bc6

source/dev/dev_guide.rst

@@ -534,7 +534,9 @@ For example, say you want to build the current *kms-core* development branch aga
    git clone https://github.com/Kurento/adm-scripts.git
    git clone https://github.com/Kurento/kms-core.git
    cd kms-core/
-   ../adm-scripts/kurento-buildpackage.sh --install-kurento 6.12.0
+   ../adm-scripts/kurento-buildpackage.sh \
+       --install-kurento 6.12.0 \
+       --apt-add-repo
 
 Run ``kurento-buildpackage.sh --help``, to read about what are the dependencies that you'll have to install to use this tool, and what are the command-line flags that can be used with it.
 
@@ -556,7 +558,8 @@ For example, say you want to build the current *kms-core* development branch aga
    docker run --rm \
        --mount type=bind,src="$PWD",dst=/hostdir \
        kurento/kurento-buildpackage:xenial \
-       --install-kurento 6.12.0
+           --install-kurento 6.12.0 \
+           --apt-add-repo
 
 
 

source/user/troubleshooting.rst

@@ -46,12 +46,20 @@ Then, please provide us with information about the crash:
 
 * If you installed Kurento with :ref:`apt-get install <installation-local>`, *and* `Apport <https://wiki.ubuntu.com/Apport>`__ is installed, then Ubuntu generates a **crash report** that you will find in ``/var/crash/_usr_bin_kurento-media-server.<PID>.crash``. This contains information that can be used to inspect KMS with a debugger, so it can be very useful to find the cause of the crash. Upload it somewhere, or attach it to your bug report.
 
+  .. note::
+
+     The *.crash* report file **is already compressed**, so you can go ahead and upload it to some file transfer service to share it with us.
+
   .. note::
 
      The *.crash* report file **must be deleted** afterwards. *If an old crash report exists, new ones will not be generated*. So if you are experiencing crashes, make sure that the crash report file is always deleted after having shared it with us, so future crashes will also generate new report files.
 
 * Otherwise, you can manually enable the generation of a **core dump** whenever KMS crashes. For this, edit the file ``/etc/default/kurento-media-server`` and uncomment the setting *DAEMON_CORE_PATTERN*, which by default will tell the Linux Kernel to generate core dumps in ``/tmp/``.
 
+  .. note::
+
+     The *core dump* file **is NOT compressed**, so before uploading you should compress it, for a typically huge file size reduction, before uploading it to some file transfer service and sharing it with us.
+
 * As a last resort, if no crash report can be obtained by any means, you may need to run KMS with a debugger. To do so, please follow the instructions here :ref:`dev-gdb`, to get a **backtrace** when the crash happens.
 
 * Finally, if a developer suspects that the crash might be due to a memory corruption error, we could ask you to run with a special build of Kurento that comes bundled with support for `AddressSanitizer <https://github.com/google/sanitizers/wiki/AddressSanitizer>`__, a memory access error detector.