-Linux

Systems will need the gdb package installed for this to work. Stack traces should be generated on the machine where the core dropped to ensure that precisely the correct version of each library is available.

First, move to the installation root directory -

$ cd /opt/Axway/apigateway/

Then run gdb on the core. Note that there are two paths in the command we use: vrun gdb /path/to/vshell /path/to/core If you don't supply the path to vshell, it will generate a stack trace with no debugging information that will not be usable. If you get the name or path of the core wrong, gdb will give you a "No such file or directory." error. Note that in the sample that follows, you are to type the commands that come after the (gdb) prompt, such as 'where' and 'info shared' in the order shown in the sample. The purpose of the commands is to tell gdb to open a log file called core_info.txt and to have gdb print some information into that log. It is this core_info.txt file that you want to send to Axway support.

$ ./posix/bin/vrun gdb ./platform/bin/vshell /core

(gdb) set logging file core_info.txt
(gdb) set logging on
Copying output to core_info.txt.
(gdb) where
(gdb) info shared
(gdb) thread apply all bt full
<return multiple times until no more output>
(gdb) set logging off
Done logging to core_info.txt.

- Solaris

$ cd INSTALL_ROOT
$ pstack core.PID > core_info.txt