User Tools

Site Tools


tutorials:troubleshooting:coredumpfile

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Last revision Both sides next revision
tutorials:troubleshooting:coredumpfile [2018/01/02 11:33]
miconda created
tutorials:troubleshooting:coredumpfile [2018/01/02 11:37]
miconda [What do do with a core file]
Line 2: Line 2:
  
  
-[color=blue]Getting the backtrace from a core file dumped upon Kamailio crash[/color]+**Getting the backtrace from a core file dumped upon Kamailio crash.**
  
 After a crash of the server it may generate a core file in its working directory, if the functionality is not disabled. This core file can be used to get the cause (or at least a hint) of the crash. The core file contains the memory of the process at the moment it crashes as well as the execution trace, so it could contain sensitive data. After a crash of the server it may generate a core file in its working directory, if the functionality is not disabled. This core file can be used to get the cause (or at least a hint) of the crash. The core file contains the memory of the process at the moment it crashes as well as the execution trace, so it could contain sensitive data.
Line 19: Line 19:
 </​code>​ </​code>​
  
-(Substitute the paths to match your installation.)+Substitute the paths to match your installation, for example:
  
-After gdb finished to read its input type **backtrace**gdb will then output the backtrace. This information should added to your bug report of the crash. Please don't delete the core files after the backtrace generation, as its really helpful for eventual further investigations.+<​code>​ 
 +gdb /​usr/​local/​sbin/​kamailio /​home/​corefiles/​core.1234 
 +</​code>​ 
 + 
 +After gdb finished to read the input and shows its promptexecute: 
 + 
 +<​code>​ 
 +backtrace 
 +</​code>​ 
 + 
 +or the short variant: 
 + 
 +<​code>​ 
 +bt 
 +</​code>​ 
 + 
 +GDB will then output the backtrace. 
 + 
 +More useful could be the full backtrace, that can be seen with: 
 + 
 +<​code>​ 
 +bt full 
 +</​code>​ 
 + 
 +This information should added to your bug report of the crash. Please don't delete the core files after the backtrace generation, as its really helpful for eventual further investigations.
  
-In order to get a meaningful backtrace gdb needs some debugging informations in its binary. If you compiled from the source, no additional steps should be necessary from you. If you install a binary package, e.g. from debian, you need to install the **-dbg** package too.+In order to get a meaningful backtrace gdb needs some debugging informations in its binary. If you compiled from the source, no additional steps should be necessary from you. If you install a binary package, e.g. from debian, you need to install the **-dbg** package too (e.g., kamailio-dbg...deb).
  
 If you don't understand the information that gdb prints, some developer on the mailling list should be able to help you. If you don't understand the information that gdb prints, some developer on the mailling list should be able to help you.
tutorials/troubleshooting/coredumpfile.txt · Last modified: 2019/11/05 10:05 by miconda