[support]

Hi,

Thanks, this sounds like a way to improve usability, however unfortunately CMake doesn’t expose this information in the data that VisualGDB uses in the Advanced CMake subsystem. We will look into patching CMake to make it report this structure, but we cannot promise that it will work until we investigate it in more detail.

[support]

Hi,

The custom rules defined for Windows projects might not work out-of-the-box for Linux. Please try following our Qt MSBuild tutorial for a detailed example of defining rules for running custom tools on Linux. If you have any further questions, please feel free to share more details about your current setup (e.g. what exact rules you are using) and we will try to help you.

[support]

Hi,

Yes, we are aware that VS2017 has basic Linux support and we are ensuring that VisualGDB has always more to offer – Powerful Linux-friendly IntelliSense, Static/Dynamic analysis, Custom actions, Profiling, Code Coverage, automatic error detection and many more features (see our Linux features page).

Our MSBuild backend is also very heavily optimized for large remotely built projects and works faster than the regular VS2017 backend.

Thanks for your suggestion. Currently editing .vgdbsettings files one-by-one could be indeed unnecessarily time-consuming, so we are experimenting with providing convenient GUI for editing multiple .vgdbsettings files at once. We will publish a tutorial showing it once this feature is available.

In the meanwhile feel free to try out our Advanced CMake subsystem – it works much better with large projects containing multiple executables and libraries as the build is orchestrated from the Linux side and CMake running on it knows exactly how to copy/remove the files. Our Advanced CMake Project Subsystem maps common CMake settings to the familiar Visual Studio GUI, making the experience similar to developing regular Windows projects.

[support]

Hi,

Thanks for reporting this. We will try to improve the navigation bar experience for large fonts in one of the next VisualGDB releases.

[support]

Hi,

No problem, we have managed to find the previous topic you created about linker scripts: https://sysprogs.com/w/forums/topic/custom-template-exception/. If you have any further questions, feel free to post in any of the topics and we will be happy to answer them.

Regarding the startup file, do you mean the system init file, or the startup file with vectors and libc initialization?

[support]

Hi,

Thanks for the update. This should indeed work, however the project-specific templates should work as well. If anyone can reproduce the problem with the broken per-project regexes and attach a repro, we should be able to investigate and fix it.

[support]

Hi,

Sorry, that would not work currently, as the ESP-IDF is not directly compatible with MSBuild (it depends on hardcoded file order and a few other constraints). We realize that ESP-IDF is frequently updated and are working on an experimental project subsystem similar to the Advanced CMake Project Subsystem that will be able to map native ESP-IDF projects directly into Visual Studio GUI, instead of importing ESP-IDF sources to MSBuild.

We expect to release a preview build with this subsystem in the next 2-3 weeks.

[support]

Hi,

Unfortunately this is also a known limitation of the ESP32 debugging that comes from the Xtensa toolchain (the ESP32 devices are not based on the ARM core; this helps reducing the price, however makes impossible to use the mature ecosystem of the ARM tools). Please feel free to look through the post covering other limitations of the ESP32 toolchain and known workarounds: https://sysprogs.com/w/limitations-of-the-esp32-debugging/

The recommended workaround is to always have a top-level wrapper function in every thread.

[support]

Hi,

Thanks, yes, if you could send us a repro case, we should be able to fix it easily.

BTW, please try deleting the ImplicitCompilerFlags.xml file and reopening the project – unless you do that, VisualGDB will reuse the incorrect flags cached by the previous version.

[support]

Hi,

Please ensure you are using the latest VisualGDB 5.3R8. It includes special logic for handling this – if you run any command that output “Loaded symbols for <…>” via the GDB session window, it will automatically re-query and update the call stack.

[support]

Hi,

Normally you don’t need to specify anything manually if you use the new “Debug a crash dump” command. If you still get the error when using this command, please let us know.

[support]

Hi,

This looks like VisualGDB fails to initialize and the service configuration is preventing it from displaying the error message properly (likely due to missing per-user configuration files). Please try temporarily configuring the service as an interactive service so that you can see the VisualGDB error messages). Please also ensure you run VisualGDB from the same user account that you used to configure it (toolchain definitions and other settings are stored separately for each user).

[support]

Hi,

You do need to use the same target-specific gdb that you use for regular debugging. If you are using VisualGDB 5.3, you can actually open a core dump file by right-clicking on the project and selecting Debug->Debug a Crash Dump. This will automatically reuse the GDB and other settings from your project settings.

[support]

Hi,

Sorry, we didn’t mean to make it confusing. The lightning icon is actually a standard VS icon for events, so we reused it in VisualGDB.

You can also use the Debug->Exceptions menu (VisualGDB displays Linux signals there), although the VisualGDB-specific window provides more control over the way signals are handled.

[support]

Hi,

The ESP32 flashing is unfortunately indeed unreliable. It is provided by the Espressif’s ESP32 OpenOCD port, so we would advise double-checking with Espressif whether they have a hotfix for this.

We have rebuilt the OpenOCD executable using the latest patches from them here: http://sysprogs.com/files/tmp/openocd.exe;  feel free to try replacing the OpenOCD binary in the toolchain directory with it (we have not fully tested it yet).

The issue with the variables is caused by the optimization. Using any other optimization level than -O0 makes GCC optimize out some variables, however using -O0 to build ESP-IDF code results in crashes during startup. As a workaround please try setting the optimization level to -O0 for specific files you want to debug (via the regular MSBuild File Properties). This should keep the ESP-IDF framework in a usable state, while providing full debug functionality for your code.

If you encounter any further problems, feel free to contact us again and we will help you resolve them.

[Author]

Posts