VisualGDB requires an Internet connection in order to automatically download toolchains, BSPs and other components. Normally, it will automatically download

When you start a debug session with VisualGDB, it will open a GDB Session window that shows the interaction between

In order to build and debug embedded firmware using VisualGDB you will need to configure it to work with your

Toolchains are collections of tools (such as GCC, GNU Assembler or GDB) that are used to build and debug projects

VisualGDB uses the standard Linux way of specifying libraries used by the projects that relies on 3 different parameters: Library

VisualGDB includes its own Clang-based IntelliSense engine. It is specifically optimized to work with gcc-based embedded and Linux code and

In order to debug imported projects with VisualGDB you will need to manually specify the path of the debugged application.

To avoid hardcoding absolute file paths in the VisualGDB project properties files, VisualGDB defines the following project variables: $(VISUALGDB_DIR) The

VisualGDB Environment Syntax VisualGDB allows customizing the environment of the command-line tools it starts. The general environment line syntax is