Update documentation about Jack server

Change-Id: I19b4517ea72646ed61293fd15b1459732852ccb3
diff --git a/tools/README-jack-server.txt b/tools/README-jack-server.txt
index bdf7f93..00e10d5 100644
--- a/tools/README-jack-server.txt
+++ b/tools/README-jack-server.txt
@@ -146,11 +146,17 @@
 $ jack-admin server-log
 Print log pattern.
 
+$ jack-admin dump-report
+Produce a report file that can be used to file a bug.
 
 
 Troubleshooting
 ---------------
 
+Below you'll find some ways to solve some troubleshooting. If you don't find a solution, file a
+bug and attach the file produced by "jack-admin dump-report".
+
+
 If compilation fails on "No Jack server running":
 
 See "Starting the server" above.
@@ -169,9 +175,7 @@
 both in your client and server configurations. See the "Server info" and "Client info" sections.
 If it doesn't solve the problem, please report and give us additional information by:
   - Attaching your compilation log.
-  - Attaching a zip of "$HOME/.jack-server/".
-  - Attaching "$HOME/.jack-settings".
-  - Executing "lsof -i TCP:8076", "lsof -i TCP:8077" and attaching the outputs.
+  - Attaching the file produced by "jack-admin dump-report"
 
 
 If your commands fails on
@@ -184,8 +188,7 @@
 If your compilation gets stuck without any progress:
 
 Please report and give us additional information by:
-  - Running "jack-admin list-server | awk '{print $2}' | xargs kill -3".
-  - Attaching the server log to the bug (see the "Server logs" section).
-  - Executing a "jack-admin server-stat" and attaching the output.
-  - Attaching "$HOME/.jack-server/logs/outputs.txt".
-  - Executing "lsof -i TCP:8076", "lsof -i TCP:8077" and attaching the outputs.
\ No newline at end of file
+  - Attaching the file produced by "jack-admin dump-report"
+  - Restart the server by issuing commands "jack-admin kill-server; jack-admin start-server"
+
+