diff --git a/debian/changelog b/debian/changelog
index 50c3581..697249d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
 applauncherd (0.30.0) unstable; urgency=low
 
   * Fixes: NB#261960 - [TASK] "Invoker" should be able to launch applications even when "applauncherd" is not running
+  * Changes: boosted application debug documentation updated 
 
  -- Alexey Shilov <alexey.shilov@nokia.com>  Wed, 01 Jun 2011 15:09:02 +0300
 
diff --git a/doc/debug.dox b/doc/debug.dox
index 0166727..a9a3a01 100644
--- a/doc/debug.dox
+++ b/doc/debug.dox
@@ -3,12 +3,15 @@
 \section debugging Debugging
 
 To debug a launched application, the debugger must be attached
-to an already running booster process. For instance: 
+to an already running booster process. Due to security limitations
+it's required to use <B>aegis-su</B> tool from <B>aegis-dss-tools</B> package. 
+See <A HREF="https://projects.maemo.org/trac/meego-security/wiki/DisablingAegisValidator#Useaegis-sutooltogranttcbtomodechange">Use aegis-su tool...</A>
+
 
 1. Run the following command:
 
 \code
-gdb /usr/bin/applauncherd.bin $(pgrep booster-d)
+aegis-su -r tcb aegis-exec -p gdb -a CAP::sys_ptrace gdb /usr/bin/applauncherd.bin $(pgrep booster-d)
 \endcode
 
 2. Set a breakpoint to the application code and let the process