Examining core dump

To examine a core dump on remote Unix machine, use the "Examine core dump" command from the WinGDB menu. The following dialog will appear:

Some of the fields are required:

Login information: it usually consists of your user account name and the target host name or IP address. Optionally you can provide also a port number and/or a password. The syntax is "username[:password]@hostname[:port]" where square brackets denote optional parts. If you don't provide the password, another dialog will appear, prompting you for it:
Byte-order: select Big-Endian or Little-Endian according to platform which the core-dump will be examined on.
Process executable path: this should be a full path to the program for which core dump was generated. You can also open a remote filesystem browser by pressing the "..." button.
Core dump path: this should be a full path to the core dump you want to examine. You can also open a remote filesystem browser by pressing the "..." button.

The remaining fields are optional:

The path to custom initialization script - it is simple text file (more about syntax) which will run after debugger has been started. It has to be located on local machine.
Additional source directories for the process. WinGDB will use "dir" GDB command to add these directories. If you want to add many source directories then separate them with semicolon character (';').
The debug info directory for the process. WinGDB will use "set debug-file-directory" GDB command to set this directory.
The shared library prefix for the process. WinGDB will use "set solib-absolute-prefix" (it is equivalent of "set sysroot" ) GDB command to set this directory.
The shared library directories for the process. WinGDB will use "set solib-search-path" GDB command to set these directories.