[support]

Hi,

Most likely some parts of the BuildMessageRegexes.xml are invalid and this is causing an internal error in VisualGDB. Please feel free to attach your BuildMessageRegexes.xml file here and we will investigate it and improve the error message.

[support]

Hi,

Thanks for the screenshot. This looks like a stand-alone project that has all the settings specified directly. The way to disable the semihosting for this project would be to replace the reference to rdimon.specs with a reference to nosys.specs (names might be different if you created your project with an older toolchain).

An easier solution would be to create a non-standalone project, disable semihosting as described earlier, convert it to a stand-alone one and copy LDFLAGS from it (accounting for the changes you manually introduced to LDFLAGS in your project).

 

[support]

Hi,

No problem, we can help you troubleshoot this, however it looks like your VisualGDB technical support period has expired (your VisualKernel support is still actiev). In order to keep receiving technical support, please renew your license here: https://sysprogs.com/splm/mykey

[support]

Hi,

The CRLF handling should have been fixed in one of the recent maintenance releases. If anyone can confirm that the problem is still present and attach a repro file, we should be able to investigate it quickly and release a hotfix.

[support]

Hi,

It looks like your technical support period has expired. To keep on receiving technical support, please renew your license here: https://sysprogs.com/splm/mykey

[support]

Hi,

It looks like your antivirus treated a test executable that got just compiled as a part of CMake tests as a trojan:

C:\Users\<censored>\Source\Repos\WindowsProject2\WindowsProject2\VisualGDB\Debug\CMakeFiles\3.10.1\CompilerIdCXX\a.exe

We regularly check the VisualGDB releases with VirusTotal and notify the antivirus companies to update their whitelists in case VisualGDB starts triggering false positives, but this looks like the antivirus got triggered by a blank executable just built on your machine.

The only advise we could give in this situation is to use a better antivirus that doesn’t get triggered by an empty program.

[support]

Hi,

The Embedded Debug Tweaking page affects whether VisualGDB will handle the semihosting syscalls, but it doesn’t affect the firmware itself. Please feel free to attach a screenshot of your project properties page from VisualGDB Project Properties so that we could advise on the exact setting name.

[support]

Hi,

No problem. We are switching a considerable amount of pages/controls in each release.

[support]

Hi,

Looks like the TestFramework.cmake file got generated incorrectly (test frameworks are not fully supported for advanced CMake projects). Please try adjusting it to target_link_libraries(<target name> pthread).

[support]

Hi,

OK, no problem, let us know if you decide to try out the pseudo-project approach.

VisualGDB MSBuild projects do support environment variables and property sheets the same way as the regular VS projects do. Let us know if you need any help configuring them.

[support]

Hi,

Thanks for the screenshot. Looks like you are using the standard DPI setting, so overriding the font size on VisualGDB level would unfortunately break control positions and will make most of the text clipped.

As a workaround, please try changing the default DPI in Windows Display Properties or simply use the Magnifier to zoom to the text. We will fully support inheriting the VS font size once we fully switch the properties window to WPF in a few releases from now.

[support]

Hi,

You can disable the regular semihosting via VisualGDB Project Properties -> Embedded Project -> Implementations for _sbrk(), etc. -> Minimal (no semihosting).

You also need to remove the reference to the advanced semihosting/profiler framework via the Embedded Frameworks page.

[support]

Hi,

OK, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2058.msi

Please also follow the instructions in this tutorial to work around the optimization bug in the original Python 3 package.

[support]

Hi,

The easiest way to handle this would be by adding custom build rules. We have a tutorial describing a similar process for integrating the Qt GUI compiler; the steps for flex/bison should be very similar.

[support]

Hi,

The easiest way to work around this is to create a separate pseudo-project (e.g. using the Custom project wizard), that will copy the root directory to the Linux machine, and reference it from the other projects. Let us know if you need more details on setting this up.

[Author]

Posts