I've seen two cases where users tried to debug a sssd process, but the gdb session kept being interrupted by SIGRT before they could get any useful info. Point out the internal watchdog to enable the gdb session to last longer.
what about mentioning also calling teardown_watchdog?
gdb process `pgrep sssd_nss$` -ex "p teardown_watchdog()"
I think both approaches are good to advertise
BTW please rebase on top of current master so we will not have merge commit
rebased onto 6087a3b384a9a9cb4fdf5b4dcbbfd8225ebc94fd
OK, done
rebased onto 7edddd93c429895272abe5bb9ca031250bf52ce9
rebased onto 15cc90b5679ac9120a5d0a978d8c7311bb0182f1
rebased onto 4adfb23b3f4435b674fe37ba145217e2666fdeaa
Two weeks without some additional comment -> merging
Pull-Request has been merged by jhrozek
I've seen two cases where users tried to debug a sssd process, but the gdb session kept being interrupted by SIGRT before they could get any useful info. Point out the internal watchdog to enable the gdb session to last longer.