How To Launch The Debugger If Any Of The GWAVA Processes Crashes

  • 7020477
  • 14-Sep-2009
  • 07-Aug-2017


GWAVA 4,5,6


After GWAVA has crashed, what is the best way to view the backtrace?


In order to view the backtrace, follow these steps:

1) Open a SSH terminal to your GWAVA Server


2) Browse to /var/dumps

3) Type 'l' (Lowercase L) to see the most recent Core Dumps.  Find the core with the date and time closest to the present time.


4) Type gdb /opt/beginfinite/gwava/assets/bin/(process) /var/dumps/core.(process).(core number).  If running GWAVA 6 type: gdb /opt/beginfinite/gwava/assets/bin/linux/x32/(process) /var/dumps/core.(process).(core number) Depending on the program that crashed, use the correct process.  Example: If gwvsmtp crashed, type gwvsmtp after the ../assets/bin/.  Also make sure to specify the correct path to where GWAVA was installed.


5) Type 'bt' to view the backtrace

6) Type quit to exit

Note: If Core Dumps are not enabled on the server, you can also run a crashed process directly in the debugger and view the backtrace if the crash will occur again.

Follow these steps to run a process in the debugger:

1) Open an SSH terminal to your GWAVA Server.


2)  Browse to the assets/bin directory.

     GWAVA 5: cd /opt/beginfinite/gwava/assets/bin
     GWAVA 6: cd /opt/beginfinite/gwava/assets/bin/linux/x32


3)  The process you want to load into the debugger must not be running.  Type rcgwavaman status to make sure the process is shown as missing. To stop the process again, type rcgwavaman stop (process).


4) Type gdb (process) to load the GWAVA process that crashed into the debugger, for example gdb gwava.


5) Type set args /consolelog


6) Type run to start the process in the debugger.


7) When the process crashes, type bt to view the backtrace.


8) Type quit to exit

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 1439.