[support]

Hi,

Yes, sorry, it’s currently a limitation of the Clang IntelliSense engine. We may support it in further versions, but currently it won’t work unless you switch back to the native VS IntelliSense.

[support]

Hi,

The easiest way to achieve that would be to disable the normal source uploading and then do it via a custom pre-build action after running your script. If this does not work, please let us know.

[support]

Hi,

The USB communication device example only supports the CDC (communication device) class. The mass storage class requires completely different source files.

Please update to the final release of VisualGDB 5.2, then update your STM32 BSP to the latest version. Then you will be able to select “Show STM32CubeMX samples” on the Sample Selection page and pick the “FatFS_USBDisk” example that shows the use of the mass storage class.

 

Regarding the ‘import recursively’ command, it’s only supported in the Custom edition and higher. If you are using the Embedded or Linux edition, you can add the files manually (one directory at a time). The header discovery will still work as shown in the tutorial.

[support]

Hi,

If the .so library is built by a VisualGDB project, you can simply reference the project via Add->Reference. If not, you would need to manually add the following command to GDB startup commands:

set solib-search-path <directory on Windows where the .so file is located>

[support]

Hi,

Unfortunately currently there is no such trick for the .hpp file, but we will look into handling this automatically once the final v5.2 is out (beginning of the next week). Right now VisualGDB simply checks for the timestamp of the main .cpp file, but we could easily make it check the relevant file contents.

One major optimization of v5.2 is that code completion (when you type code or press ctrl-space) should work even while the 10-second ‘parse – check’ phase is active, so the 10-second delay should only affect advanced colorization of newly typed text, but not most of the normal functionality. Could you confirm that it actually works for your project?

[support]

Hi,

You can tell gdb where to look for your .so symbols using the set solib-search-path command. Normally VisualGDB should do it automatically as long as your application project references the .so project.

If it is referenced and the .so library is not found, please let us know and we will investigate and fix this.

[support]

Hi,

This happens because the gcc used in the Beaglebone toolchain is too old and does not support C++11.

Our toolchains exactly match the gcc version used natively on the board. We are planning to recheck the gcc version in the latest Beaglebone images and release an updated toolchain in the next 2-3 weeks.

[support]

Hi,

Thanks very much for reporting this. Apparently there was a bug in our MSBuild backend that caused problems with Nordic projects.

Please try this build, it includes a fix for this: http://sysprogs.com/files/tmp/VisualGDB-5.2.12.1281.msi

[support]

Hi,

We have just published a tutorial showing how to use the header discovery: http://visualgdb.com/tutorials/intellisense/headers/

If this does not help, please attach a screenshot of your Visual Studio showing the Errors pane and the text editor for the source file that has the missing headers.

Please note that the new feature only works if you are using the Clang IntelliSense.

[support]

Hi,

Thanks for the log. It looks like you have modified the main source file and then tried reparsing one of the header files. This does look like a bottleneck and we could optimize this further.

Can you confirm that code completion within the main .cpp file works reasonably fast after the trick with explicitly ending the preamble?

[support]

Hi,

The include directories are handled separately from the .h files in Solution Explorer.

The easiest way to resolve this is to update to VisualGDB 5.2 Beta 4 and let it find the missing header files automatically.

[support]

Hi,

Thanks for clarifying this. Normally the FLASH programming is handled by OpenOCD, so supporting special programming modes would involve creating an OpenOCD patch.

As this feature looks like something very specific to certain bootloader types, we would not be able to give it enough priority to push it into one of the next releases. Sorry about that.

Our best advice would be to submit a feature request to the OpenOCD community.

[support]

Hi,

No, Live Profiling uses the regular SWD/JTAG lines and does not require any extra connections. It relies on the fact that you can read/write target memory over JTAG/SWD without stopping the target and uses a simple memory buffer for communication.

[support]

Hi,

Resharper uses a separate IntelliSense engine, so unless JetBrains explicitly adds support for parsing VisualGDB projects, it may not work properly.

We do recommend using our Clang IntelliSense engine for VisualGDB projects as it is especially optimized for GCC-specific code and provides many improvements compared to the regular Visual C++ IntelliSense.

If you miss some of the features with it, please let us know and we will consider adding them.

[support]

Hi,

No problem. If you encounter further problems, feel free to contact us again.

[Author]

Posts