[icinga-checkins] icinga.org: icinga2/master: Development docs: Add own section for gdb backtrace from a running process

git at icinga.org git at icinga.org
Thu Aug 18 12:29:51 CEST 2016


Module: icinga2
Branch: master
Commit: 7b4365d529e7a9b9e6e049cbab1c833a92042cc0
URL:    https://git.icinga.org/?p=icinga2.git;a=commit;h=7b4365d529e7a9b9e6e049cbab1c833a92042cc0

Author: Michael Friedrich <michael.friedrich at netways.de>
Date:   Thu Aug 18 12:29:34 2016 +0200

Development docs: Add own section for gdb backtrace from a running process

fixes #12477

---

 doc/20-development.md |   14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/doc/20-development.md b/doc/20-development.md
index c60292c..fa4b0c0 100644
--- a/doc/20-development.md
+++ b/doc/20-development.md
@@ -158,14 +158,22 @@ If Icinga 2 aborted its operation abnormally, generate a backtrace.
     (gdb) bt
     (gdb) thread apply all bt full
 
-If Icinga 2 is still running, generate a full backtrace from the running
-process and store it into a new file (e.g. for debugging dead locks):
+If gdb crashes with a SIGPIPE error please disable the signal before
+running Icinga 2.
 
-    # gdb -p $(pidof icinga2) -batch -ex "thread apply all bt full" -ex "detach" -ex "q" > gdb_bt.log
+    (gdb) handle SIGPIPE nostop noprint pass
+    (gdb) r
 
 If you're opening an issue at [https://dev.icinga.org], make sure
 to attach as much detail as possible.
 
+### <a id="development-debug-gdb-backtrace-running"></a> GDB Backtrace from Running Process
+
+If Icinga 2 is still running, generate a full backtrace from the running
+process and store it into a new file (e.g. for debugging dead locks):
+
+    # gdb -p $(pidof icinga2) -batch -ex "thread apply all bt full" -ex "detach" -ex "q" > gdb_bt.log
+
 ### <a id="development-debug-gdb-backtrace-stepping"></a> GDB Backtrace Stepping
 
 Identifying the problem may require stepping into the backtrace, analysing



More information about the icinga-checkins mailing list