Table of Contents
Changing the preferences
WingGDB has several configuration options which can be set globally,
for all projects and sessions. To customize these options, choose
Preferences command available in WinGDB menu. The options
are divided into categories, described in subsequent sections.
All changes take effect at next debugging session.
- Default debugger path points to the gdb executable. If it is available
on search PATH on the host you run your application on, then it is unnecessary to provide
the full path. Default value for this setting is just 'gdb'. This option can also be set
on the project or solution level. This global value becomes a default value in those places.
- Default toolchain path points to directory where the tools needed for
the build are lcoated (compiler, linker, etc.). This option can also be set on the project
or solution level. This global value becomes a default value in those places.
- Xming path points to directory where Xming is installed. You need this
if you want to use the X11 forwarding feature.
- Assembler syntax: some architectures allow choice of assembler
syntax presented in the Disassembly view. You can speciy the name
of the syntax here (e.g. "att"). Available syntaxes are typically descibed
in gdb manual for particular architecture. Leave this field blank
for default syntax.
- Maximum displayed stack depth:
maximal number of frames showed in call stack. This setting prevents gdb
from hanging on large call stacks, e.g. when debugging infinite recursing programs.
- Memory page size:
On some GDB versions disassembly operation is very slow.
If you experience that problem, you can change this setting to small
power of 2, e.g. 128 or 256 to alter the page size.
This might improve the performance.
- Suppress init files: if enabled, the debugger will not execute commands
found in any standard initialization files like .gdbinit
(it doesn't affect WinGDB custom initialization script).
- Show leading zeros in formatted values:
controls the formatted numeric values display, as in the option name.
- Log session to file: when enabled, the whole gdb communication
and other diagnostic data will be dumped to a log file. Enable this option if you have
found a bug or experience any problems with WinGDB.
This option influences performance, so it should be enabled only if it is
- Enable disassembly diagnostic mode: extended diagnostic mode concerning
Disassembly View. It may be very slow, so enable it only if you experience any
problems with that kind of view. It doesn't diagnose any other features.
- Enable remote protocol diagnostic mode: extended diagnostic mode concerning
remote protocol (for Indirect and Embedded modes). It may be very slow, so enable it
only if you experience problems specific to these modes.
- Always use SSH agent to authenticate:
suppresses the password dialog and always tries to perform authentication
through SSH agent. See this section for more details.
- Always use SCP for file transfer:
forces the SCP file transfer back-end to be used instead of SFTP one. Enable this if
you have trouble with file transfer to your embedded system using SFTP protocol.
This mode uses shell commands to perform filesystem queries, as the SCP protocol
has no such functionality.
- Limit SCP upload packet size:
forces the SCP file transfer back-end to limit packet size. This prevents transfer
errors on some versions of dropbear SSH server. Enable this if you are
using dropbear and experience occasional file upload errors.
- TCP keep-alive period:
if non-zero, enables sending special keep-alive packets periodically. These packets
can prevent the connection from being dropped due to inactivity by some firewalls.
Try setting this option to e.g. 60000 when you regularly experience dropped connections.
- Always use manual shell configuration: in case of trouble with shell communication (e.g. if remote
account needs some user interaction after login) WinGDB displays a console. By default WinGDB displays it
only once and stores all user's input. If this option is enabled, then console will be displayed every time
it is needed.
- Console font: allows to change the font used by the Process Console window.
Only monospace (fixed character width) fonts are supported, like Courier family or
default Fixedsys Excelsior. Click Browse for the font selection dialog to appear.
This dialog allows you to select any font (as some monospace fonts are not marked being
monospace), however you will obtain good visual results only with a monospace font.
- Console colors: group of color settings for the Console window.
You can click Browse for the color selection dialog to appear.
The same appearance settings also exist for the remote terminal window, on
the Terminal page. You can set different fonts and colors for terminal
and process console windows.
X11 settings are described in this section.
Table of Contents
Copyright (C) 2008-2016 SOFT-ERG. All rights reserved.