tyler.durden/icinga2
1
0
Fork 0
mirror of https://github.com/Icinga/icinga2.git synced 2025-07-25 14:44:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source 
fixes #12477
This commit is contained in:
Michael Friedrich 2016-08-18 12:29:34 +02:00
parent 487d2a9907
commit 7f9130fa1c
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/20-development.md
View File

@ -158,14 +158,22 @@ If Icinga 2 aborted its operation abnormally, generate a backtrace.
(gdb) bt (gdb) bt
(gdb) thread apply all bt full (gdb) thread apply all bt full
If gdb stops at a SIGPIPE signal please disable the signal before
running Icinga 2.
(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 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): 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 # gdb -p $(pidof icinga2) -batch -ex "thread apply all bt full" -ex "detach" -ex "q" > gdb_bt.log
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-stepping"></a> GDB Backtrace Stepping ### <a id="development-debug-gdb-backtrace-stepping"></a> GDB Backtrace Stepping
Identifying the problem may require stepping into the backtrace, analysing Identifying the problem may require stepping into the backtrace, analysing