[support]

Hi,

Thanks for confirming this. We have added background execution for custom shortcuts to v5.3 roadmap. We will post an update here once this feature is available.

[support]

Hi,

Yes, please check the ‘Allow choosing build/clean/debug command hosts independently’ checkbox on the Project Settings page of VisualGDB Project Properties.

[support]

Hi,

VisualGDB normally does exactly that – captures the #define-s reported by gcc and feeds them into the Clang IntelliSense. If you are using MSBuild projects, you can see a list of those via View->Clang IntelliSense Diagnostics Console ->View->ProjectStatus->CFLAGS (due to a bug in the Windows edit control, it may appear empty if CFLAGS is too long; copy-pasting it to notepad should help). If you are using non-MSBuild projects, the flags are dumped in gcc_<configuration name>.h and this file is forcibly included by the Clang engine.

If you believe this is not happening, please let us know the details (which macros are missing from the IntelliSense point of view) and we will help you troubleshoot this.

[support]

Hi,

Sorry about that, this is a bug of the new mbed BSP that is in the Beta stage.

To fix this, please copy the  %LOCALAPPDATA%\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.stm32\STM32F4xxxx\DeviceDefinitions\stm32f446xx.xml.gz file to %LOCALAPPDATA%\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.mbed\DeviceDefinitions\stm32f446xx.xml.gz and add the following line to the mbed.xml file in your project directory under the EmbeddedProfile element:

  <MCUDefinitionFile>DeviceDefinitions/stm32f446xx.xml</MCUDefinitionFile>

This will automatically pick the register definitions from the normal STM32 package.

[support]

Hi,

We currently don’t have any specific plans for supporting visualization of std::multimap or boost::fusion::vector, however VisualGDB offers 2 mechanisms that allow adding custom type visualizers easily:

• You could use the C# type visualizer API
• Alternatively you could use the Natvis files

[support]

Hi,

Yes, you can do that by pressing the Signals button in the GDB Session window, going to the Catchpoints page and selecting “Break on throwing an exception”.

[support]

Hi,

It is hard to say what could be wrong based on this description. Please try debugging your program by pressing F5 in Visual Studio and step through the initialization code to see what is wrong.

[support]

Hi,

Sorry about that. Looks like our BSP is missing a reference to the library that provides those functions.

Please add the <SysGCC>\esp32\esp32-bsp\esp-idf\components\bt\lib\libbtdm_app.a file to your project manually and the Bluetooth functions should get linked properly.

[support]

Hi,

Sorry, we still could not reproduce this. Looks like it is caused by the directory layout on your Linux machine. We have added some extra logging to the latest VisualGDB 5.2R4.

Please try downloading it, then open View->Other Windows->VisualGDB Diagnostics Console and reproduce the problem. Once the problem is reproduced, please attach the diagnostic log contents here so that we could pinpoint this.

[support]

Hi,

Sorry for the delayed reply. When you are using a cross-toolchain, VisualGDB builds the code on the Windows side and then deploys the file to the Linux machine and runs gdb on Windows (same machine that builds the code).

In order to follow the steps above, please copy the current configuration via the VisualGDB Project Properties and change the build machine for that configuration to be your deployment machine. Then follow the steps described earlier to configure debugging.

For your convenience we have made screenshots of the relevant settings:

The /tmp/path-to-executable should match the location on the Linux machine where your executable is deployed.

Note that this configuration should not be used to build the project, it’s just a workaround to start debugging with gdb on a different machine without using the features of the Custom edition.

[support]

Hi,

Please try following the instructions from the this page on referencing prebuilt libraries from other modules.

[support]

Hi,

Sorry about that. Could you try switching OpenOCD to manual mode, disabling the interface/target scripts and specifying the board/ek-tm4c1294xl.cfg board script?

If this does not help, please try it on a different computer. Perhaps some other software or driver is interfering with OpenOCD.

[support]

Hi,

Sorry about that. Please send the dump file created by the IntelliSense engine via our support form and we will send you a hotfix (or a diagnostic build to pinpoint it better) within 48 hours.

The temporary build links automatically expire when their functionality is moved to the normal releases. If the same problem occurs with build 1297, it is probably caused by something else and we would need a dump file to pinpoint/fix it.

[support]

Hi,

As most of our users rely on GCC, we indeed do not directly support the IAR compiler. It is possible however to modify a VisualGDB project to use any 3rd-party compiler.

We do have a detailed tutorial showing how to use the Keil ARM compiler with VisualGDB here: http://visualgdb.com/tutorials/arm/keil/; adding support for IAR should be very similar.
The steps described there only work for Make projects; MSBuild would require slightly different steps, but we could guide you through them.

As Visual Studio itself does not support per-folder options, VisualGDB can’t do that out-of-the-box. You can achieve this by adding a few custom targets to your MSBuild project, but it won’t be easily configurable via GUI. Let us know if you want to go that way and we could give you a basic example.

P.S. If the only reason you are not using GCC is the lack of support for multiple memory regions, we could provide you with a custom tool that will re-link an existing ELF file to spread one data section across multiple regions using the relocation records generated by the compiler. If you are interested, please contact our sales and we will give you a quote for making this tool.

We currently don’t have any plans for supporting IAR compiler directly as it is not very popular among our users. We could add it as a paid customization if you believe this could save time, or we could just help you support it on your side by customizing VisualGDB projects.

[support]

Hi,

Thanks for clarifying this. When we made the tutorial, we could not get any errors with the original extern “C” block.

Please feel free to post the errors you got so that we could check what could be causing this.

[Author]

Posts