pom-ng:troubleshooting
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Previous revision | |||
— | pom-ng:troubleshooting [2020/05/26 21:59] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Troubleshooting ====== | ||
+ | |||
+ | ===== Crash / Segmentation fault ==== | ||
+ | |||
+ | In order to troubleshoot crashes, pom-ng must be compiled with debug information : | ||
+ | |||
+ | # ./configure CFLAGS=" | ||
+ | # make clean | ||
+ | # make | ||
+ | # make install | ||
+ | |||
+ | |||
+ | This step is very important in order to find out where the crash occurs. | ||
+ | |||
+ | The best way to identify where the crash occurs is to run pom-ng inside gdb : | ||
+ | |||
+ | # gdb pom-ng | ||
+ | GNU gdb (Gentoo 7.5.1 p2) 7.5.1 | ||
+ | [...] | ||
+ | Reading symbols from / | ||
+ | (gdb) | ||
+ | | ||
+ | Once gdb is started you need to run the program and reproduce the crash : | ||
+ | |||
+ | (gdb) run -d 5 | ||
+ | Starting program: / | ||
+ | [...] | ||
+ | |||
+ | When the crash occurs, you'll get back to the gdb prompt. Here is an example : | ||
+ | |||
+ | [...] | ||
+ | datastore: Error while locking mutex in datastore.c: | ||
+ | Program received signal SIGABRT, Aborted. | ||
+ | [Switching to Thread 0x7fffdbfff700 (LWP 13470)] | ||
+ | 0x00007ffff5d09015 in raise () from / | ||
+ | (gdb) | ||
+ | | ||
+ | The command "bt full" will already provide a lot of informations about the issue : | ||
+ | |||
+ | (gdb) bt full | ||
+ | #0 0x00007ffff5d09015 in raise () from / | ||
+ | No symbol table info available. | ||
+ | #1 0x00007ffff5d0a48b in abort () from / | ||
+ | No symbol table info available. | ||
+ | #2 0x00007ffff7bc8ee1 in datastore_connection_new (d=0x62ab70) at datastore.c: | ||
+ | err_num = 22 | ||
+ | res = 0x7fffdbffe930 | ||
+ | [...] | ||
+ | (gdb) | ||
+ | |||
+ | |||
+ | |||
+ | *** Make sure you provide the full output of gdb (even before you run the pom-ng if possible) in your bug report.*** |
pom-ng/troubleshooting.txt · Last modified: 2020/05/26 21:59 by 127.0.0.1