[support]

Hi,

Normally VisualGDB should handle this automatically. Please let us know an example error message you get and we will suggest how to resolve this.

[support]

Hi,

This looks like a bug. Could you try removing the %LOCALAPPDATA%\VisualGDB\RemoteSourceCache\192.168.1.27 directory and reloading the directories? If the problem is reproduced, could you send us your .vgdbsettings file and the .vxcproj file so that we could try reproducing it on our side?

[support]

Hi,

This could be an indication of a bug in gdb/gdbserver. Could you double-check via the gdb command log that the “set follow-fork-mode child” command is accepted correctly and not overridden later?

Can you also reproduce the problem with a regular command-line gdb?

[support]

Hi,

Our latest STM32 BSP does support the STM32F769 board. Perhaps you are using an older version of VisualGDB that is not compatible with the latest BSPs?

The latest STM32 BSP is v4.0 and the latest VisualGDB is v5.2.

[support]

Hi,

Yes, this should work. Perhaps the problem is related to symbols? Does hardcoding a breakpoint in the child process (asm(“bkpt 255”)) trigger properly?

[support]

Hi,

Please try the latest v5.2R2 and retest your toolchain. It should generate the following definition for __cplusplus

#undef __cplusplus
#define cplusplus <version>

This should fully override the default value on all VS versions.

[support]

Hi,

The “import folder recursively” feature is available starting from the Custom edition. You can always upgrade your VisualGDB here: https://sysprogs.com/splm/mykey

Regarding MBED_CONF_NORDIC_UART_HWFC, it’s a known issue of the current mbed 5.2 beta BSP. It can be safely ignored and will be resolved in the final release.

[support]

Hi,

Please try switching the debug method to full-custom mode. Then specify the following:

Arguments	–interpreter mi $(TargetPath)
Working directory	$(ProjectDir)
Target selection command	source connect.gdb
Start command	Assume the target is already stopped

Then create a file called connect.gdb in your project directory and paste the attaching commands there:

target extended-remote COM3
attach 1

Then finally go to the Additional GDB Commands page and add the following post-target command:

load

[support]

Hi,

You may want to create a separate Linux and Windows configurations for that. Please check this tutorial: http://visualgdb.com/tutorials/porting/linux/

[support]

Hi,

VisualGDB supports STL containers out-of-the-box and provides 2 mechanisms to support custom structures:

• Type visualizers
• Natvis

If you believe some of those are not working properly, feel free to start another topic with details and we will investigate.

[support]

Hi,

You can do that via Visual Studio Project Properties -> C/C++->Advanced->Language standard for C files.

[support]

OK, we have added it to this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.13.1294.msi

[support]

Hi,

Please try the final VisualGDB 5.2 release. It contains the fix mentioned here.

[support]

Hi,

This could be caused by a problem that was solved in VisualGDB 5.2. Please try updating to it and resynchronize your toolchain sysroot.

[support]

Hi,

No problem. Library names can sometimes be confusing. Generally searching for *.so and *.a files containing the missing function name usually finds the correct one quickly.

[Author]

Posts