From 4adfb23b3f4435b674fe37ba145217e2666fdeaa Mon Sep 17 00:00:00 2001
From: Jakub Hrozek <jakub.hrozek@posteo.se>
Date: Oct 24 2017 14:22:05 +0000
Subject: reporting bugs: Hint on increasing the timeout


---

diff --git a/users/reporting_bugs.rst b/users/reporting_bugs.rst
index 0bc6d01..cc1efbe 100644
--- a/users/reporting_bugs.rst
+++ b/users/reporting_bugs.rst
@@ -103,6 +103,26 @@ When the program crashes, save the core file and backtrace::
 
 Then attach the core file and the backtrace.
 
+When connecting to a sssd process with ``gdb``, you should increase the
+``timeout`` option in the debugged process's section up from its default
+value, such as::
+
+    [domain/test]
+    id_provider=ldap
+    ....
+    timeout = 300
+
+If you don't do this, chances are that ``gdb`` will be interrupted by SSSD's
+internal watchdog (which manifests as SSSD receiving ``SIGRT``) before you
+can catch the error you're debugging.
+
+Alternatively, you can disable the watchdog from inside the gdb session::
+
+    gdb process `pgrep sssd_be` -ex "p teardown_watchdog()"
+
+This has the advantage of not having to restart the sssd, on the other hand,
+the watchdog is also disabled for the single gdb session only.
+
 Mind your privacy
 -----------------