[support]

Hi,

Thanks for your input. We have added it to the backlog and will try to address it in one of the next major releases, although as this is something very specific and low-impact, the relative priority of this feature is currently low.

[support]

Hi,

Sorry, as this case is very specific, we don’t have a tutorial fully covering it. Our best suggestion would be to look through OpenMP documentation and tutorials on their site to get a basic overview of it. That said, we will be happy to help you locate the relevant VisualGDB settings if you are experiencing troubles getting your project to work with VisualGDB.

[support]

Hi,

This could happen if we missed some scenario. Please let us know what exactly do you mean by “paths not recognized”. If you get a specific error message while trying to build or debug a project, please ensure you quote the entire error text and also let us know what exactly triggers it.

[support]

Hi,

Please try reproducing it on a newly created project. You might have accidentally overridden some settings that control temporary breaks for setting breakpoints. If the problem does not reappear on a newly created project, please compare the .vgdbsettings files of both projects.

[support]

Hi,

Please use the Qt Designer tool (or Qt plugin for VS). It will provide basic functionality for editing the UI files, although it is not as comprehensive as the WinForms/WPF editors.

[support]

Hi,

Thanks for the suggestion. As this is a fairly low-impact issue, we don’t want to add another dependency to a 3rd-party library like libmagic, however you could work around it by running it on your side and generating a list of exceptions to include/exclude.

To facilitate this, we have added support for the exclusion syntax to this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2187.msi

You can now use the “-ext1;-ext2;*” syntax to treat all file extensions except the explicitly entered exceptions as executables.

[support]

 

Hi,

No problem. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2187.msi

VisualGDB will show the link to a new version once it becomes a stable release. Currently VisualGDB 5.4 is a preview build (i.e. introduces new features, but might be unstable), so we intentionally don’t show it in the update GUI to avoid breaking users who prefer waiting for the stable release.

 

[support]

Hi,

The InitializeFastSemihosting() function is normally invoked at the start of your debug session so that VisualGDB will start reading the output from the fast semihosting mechanism. Normally VisualGDB should handle this breakpoint internally and not show the “Sigtrap” message.

If you get this breakpoint in the middle of the debugging session, most likely your program corrupts the memory and/or restarts unexpectedly. If it only happens during session initialization, please try comparing the full gdb logs for the normal session and the crashed session and check for any obvious differences (e.g. gdb errors). If you are not sure, feel free to post both logs here and we can take a look.

[support]

Hi,

This looks like a problem inside the Segger gdb stub. Please check with Segger support whether they have a fix for this.

[support]

Hi,

Thanks for letting us know. The FetchContent module looks new, so most likely it was not yet available in the version used in our build. This should get fixed automatically once we update our pre-built CMake from the latest sources.

[support]

Hi,

Sorry for the delay. We have added experimental support for relative paths in CustomToolchain.xml (using the $(ToolchainDir) syntax) to this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2185.msi

Let us know if it works for you (you will need to delete the CustomToolchain.xml file and re-import it in order to get the correct path syntax).

[support]

Hi,

Thanks, this is a known limitation of the “del” command. As a workaround, please try setting USE_DEL_TO_CLEAN := 0 in your <config>.mak file (if your toolchain as the rm tool), or simply edit the Makefile to use backward slashes or specify quotes (only in the clean command line).

[support]

Hi,

This is by design. VisualGDB 5.3 and later does not store the toolchain location anywhere in the project files, letting you build your projects without modifications on computers with different toolchain locations. When building with VisualGDB, the TOOLCHAIN_ROOT variable is computed dynamically and set before invoking Make. If you want to run Make manually, you need to set TOOLCHAIN_ROOT explicitly (or hardcode it in the Makefile using the ?= syntax if you are OK with storing it there).

[support]

Hi,

Thanks for the screenshots. It looks like a known issue. Unfortunately the ST-Link v2 has a bug that prevents it from reporting its USB serial number the way OpenOCD can read it. This has been fixed in ST-Link v2.1 (that is installed on most newer boards). Please either try upgrading your board, or check if there is a firmware update that will turn your ST-Link into v2.1.

You can also try locating and applying ST’s patches to OpenOCD that resolve this, however in our experiments they introduced strange side effects, so we ended up not including them in our OpenOCD build.

[support]

Hi,

Sorry for the delay, we have been receiving a larger amount of inquiries than usual. We will respond to your support ticket within the next 24 hours.

[Author]

Posts