[support]

Hi,

For Arduino projects VisualGDB relies on the regular Arduino build process (arduino-builder.exe) that does not support adding arbitrary resources. The only exception is the SPIFFS file system that is only available when using the ESP32 Arduino core. VisualGDB supports it starting from the Custom edition as shown in this tutorial.

[support]

Hi,

J-Link indeed typically works better than ST-Link, and it comes with its own fully tested and supported GDB stub that replaces the open-source OpenOCD. VisualGDB supports both OpenOCD and J-Link software via interchangeable debug plugins, so our users can pick the debug probe that works the best for their setup.

[support]

Hi,

As per the VisualGDB feature table, unit tests are supported by the Ultimate, Android and Custom editions.

[support]

Hi,

According to our records, your trial has expired. We can gladly investigate this further, however we would kindly ask you to purchase a license first.

[support]

Hi,

No problem. The warning about spaces in path is meant for a different package type. CMake can be safely installed into paths with spaces.

We have updated VisualGDB internally to not show it when installing CMake and will include this fix in the next VisualGDB update.

[support]

Hi,

This looks like an incompatibility between some feature of the Qt framework and XMing (the tool for showing Linux X11 GUI on Windows). You can work around it by manually installing and launching vcxsrv a more modern build of Xming. If it doesn’t help, please try switching your project to show the GUI on the Raspberry Pi itself (via VisualGDB Project Properties -> Debug Settings).

[support]

Hi,

No problem. We have rechecked the handling of CommonExecutablePath and ExecutablePath by the regular VC++ projects and updated VisualGDB to replicate its behavior.

Please try this build: VisualGDB-5.6.1.4083.msi

[support]

Hi,

For all questions related to licensing, activations, renewals and quotes, please contact our sales via the contact form.

[support]

Hi,

No problem, you can set the CommonExecutablePath property by manually adding the following lines to the .vcxproj file:

<PropertyGroup>
    <CommonExecutablePath>[Value]</CommonExecutablePath>
</PropertyGroup>

[support]

Hi,

It’s hard to suggest something specific here because the variable logic is handled by the Visual Studio itself rather than VisualGDB. You can try reproducing the problem on a regular non-VisualGDB project using the Exec task and then contact Microsoft for help.

If the VisualGDB projects behave differently from the regular MSBuild projects, please let us know and we will help you replicate the regular VC++ behavior.

[support]

Thanks, we have confirmed that the new module attribute layout is also used in the 5.4 kernel branch after the v5.4.52 release. We have updated the check accordingly. Please try downloading the new installer.

The “no such host is known” error typically means that  the machine running GDB cannot resolve the host name of the target. The easiest way to work around it would be to use IP addresses instead of host names in the settings.

If it doesn’t help, please share the screenshot of the error message you get, and any diagnostic logs or traces shown in it, and we will help you resolve it.

[support]

We have rechecked it. Please try restarting the target and clearing the /tmp directory if it contained the previous version of LinuxKernelDebugHelper.

If it doesn’t help, please double-check that the SequentialModuleInfo.c file copied to the target contains the USE_NEW_MODULE_ATTRIBUTE_LAYOUT check and that the check is enabled when building on your kernel (e.g. add an #else \\ #error Unexpected ) after the Linux kernel version check.

If it doesn’t help either, please let us know the output of running the “uname -a” command on the target machine.

[support]

Hi,

This likely happens because the header file is referenced by one of the source files inside the BSP (i.e. imported from the STM32CubeMX template) and not inside the application itself.

Please try selecting the BSP instead of the application when adding the discovered include directories to the project settings. If adding the directories to BSP doesn’t work, please try this build: VisualGDB-5.6.1.4079.msi

[support]

Hi,

No problem, we have reproduced and fixed the issue. Please try updating to VisualKernel 3.1R8 here: https://sysprogs.com/VisualKernel/download/

[support]

No problem, please let us know the email address associated with your license key, so that we could check your support status.

[Author]

Posts