[support]

Hi,

No problem, we will be happy to clarify this here.

The Embedded Frameworks is a convenient shortcut for adding/removing groups of source files (and associated flags) to the project. E.g. if your project references the “FreeRTOS” framework, VisualGDB will automatically add the related sources, include directories and preprocessor macros to the project. Furthermore, if the exact settings change after a BSP update, you will be able to update your project by simply regenerating BSP-related files. The embedded frameworks have a varying degree of accuracy depending on the platform. For platforms that provide structured definition of components they are automatically derived from those definitions. For Nordic devices they are derived from scanning the source folders during our BSP build process and applying a set of simple rules.

The files added via Embedded Frameworks are placed under the “Device-Specific Files” folder in Solution Explorer. This folder is managed by VisualGDB and any changes you make under it (e.g. new files/removed files) will be overwritten next time you regenerate the BSP-specific files. This is by design as it allows updating the project when the list of the sources corresponding to a specific framework changes. All files added to other folders in Solution Explorer (and the “Excluded from Build” flag on the files originating from the frameworks) will be preserved.

Our example projects may indeed include many extra frameworks, as the internal structure of the SDK changed considerably and we have not optimized this yet. The good news is that the link-time garbage collection should take care of this, so the size of the final binary will not be affected.

Thanks for the suggestion with the app templates, we will investigate the possibility of wrapping them as VisualGDB project templates and will include them unless we discover some blocking issues.

[support]

Hi,

It looks like an incompatibility between the debug information format stored in the object files and valgrind. You might be able to resolve it by explicitly forcing the debug format to an older version of DWARF by adding “-gdwarf-2/3/4” to the CFLAGS/CXXFLAGS.

You can access advanced VisualGDB logs (that include all command lines launched via SSH) via View->Other Windows->VisualGDB Diagnostics Console.

You can add extra arguments to Valgrind via the “Additional Valgrind flags” field in the New Profiling Session window.

If you need any further help, do not hesitate to get back to us.

[support]

Hi,

The OpenOCD build that is included in our toolchains includes some fixes and usability improvements compared to the original ESP32 OpenOCD. You can get the source code (including a VisualGDB project for convenient building with CMake) here: https://github.com/sysprogs/openocd-esp32

For your convenience we have merged the latest commits from the Espressif’s branch into our fork and uploaded a built version here: http://sysprogs.com/files/tmp/esp32/openocd.exe

[support]

Hi,

This looks like VisualGDB is not able to extract the FLASH programming parameters from the esptool command line. We would need to see the BuildCommandLines.txt file from the VisualGDBCache directory in order to diagnose this further.

 

[support]

Hi,

Sorry about that, looks like our bug. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.3.2365.msi

 

[support]

Hi,

Strange. This might come from some settings cached by the previous build. Could you please try creating a new “blink” project using the latest IDF from scratch? If this works, please try deleting the VisualGDBCache directory in the original project and then re-open it.

[support]

Hi,

Thanks you for purchasing VisualGDB. We have prepared a preview build including this fix: http://sysprogs.com/files/tmp/VisualGDB-5.4.3.2363.msi

If the ESP32 debug package fails to initialize, please replace the file <toolchain>\esp32-bsp\sysprogs\debug\core\ESPxxDebugPackage.dll with the following one: http://sysprogs.com/files/tmp/ESPxxDebugPackage.dll

 

[support]

Hi,

Please let us know the email associated with your license key so that we could check your support status.

[support]

Hi,

Thanks for the detailed explanation. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.3.2362.msi

Then enable the Clang Format-based formatting engine via Tools->Options->Text Editor->C/C++ (VisualGDB)->Formatting Engine and reopen your project.

It will handle the formatting settings you mentioned correctly and will also let you tweak various advanced formatting settings via a graphical formatting style editor that can be opened via the “format” icon at the top right corner of the source file editor.

[support]

Hi,

We have internally added support for the Renesas RL78 family that will be included into the upcoming VisualGDB 5.4 Preview 4.

We could post an update here once we release it. If you are looking for a different Renesas family, please consider following our legacy device tutorial to setup a project manually.

[support]

Hi,

Sorry, this is a part of our licensing policy and we would not be able to remove it.

[support]

Hi,

Sorry, it is a part of our licensing policy to display the user name in the About window and the GDB session window. It is not shared with any other users or parties and is only shown on the actual computer where VisualGDB is installed. If you do not want others to see the licensing information, please use video editing software to blur/remove any sensitive information.

[support]

Hi,

The best way to diagnose this would be to narrow it down to a specific component. Please try attaching to the target process by running gdb directly from command line. Do you observe the same behavior?

If not, please enable the GDB command timing view in the GDB Session window and check if the delay comes after any specific command (you can also enable the creation of detailed gdb logs via Advanced GDB Settings – the created logs will contain timestamps for every line).

[support]

Hi,

Good to know it works.

You can customize the tab/space behavior for VisualGDB projects via Tools->Options->Text Editor->C/C++ (VisualGDB).

If it doesn’t help, please provide a specific example (exact steps, expected behavior, actual behavior) and we will help you configure VisualGDB accordingly.

[support]

Hi,

Normally VisualGDB should automatically download/install a compatible XMing version. Please try installing the latest VisualGDB 5.4 Preview 3 and then reset the XMing location via Tools->Options->VisualGDB->General->Tools->Full path to xming.exe.

Next time you start debugging, VisualGDB will suggest automatically installing xming. Please proceed with the installation and ensure your firewall/antivirus doesn’t block it from running and accepting connections.

[Author]

Posts