Forum Replies Created
-
Posts
-
Hi,
Normally, the disassembly warning should not crash Visual Studio. If this happens, please feel free to obtain a stack trace of the crash, and attach it here along with your VisualGDB build number.
You can also increase the disassembly deactivation timeout via settings (Tools->Options->VisualGDB->General->Debug->Disassembly reading timeout).
Hi,
The logic that copies the file first time you change it indeed doesn’t resolve the variables (we will fix it in the final v5.6 release), and will try to use an incorrect name, however the rest of the GUI will work just fine, as long as you create the sdkconfig-debug and sdkconfig-release files manually.
The GUI for editing the configuration values queries the full path to the SDKConfig file from the ESP-IDF build subsystem, so it will always edit the configuration for the currently loaded configuration. If you would like to edit settings for another configuration, please select it in the VS configuration manager first, so that VisualGDB can query its layout from the ESP-IDF build scripts.
Hi,
Please try running vgagent.exe manually (e.g. vgagent.exe cmd.exe should start cmd.exe). If it’s not starting, something on your computer is preventing it from starting.
Thanks for your feedback. Just to clarify, do you mean the list of all functions in the current source file, or in the entire solution?
Thanks for renewing your licenses today. Please find the detailed answer to your inquiry below.
The way VisualGDB stores settings for different configurations depends on the project type. For VC++-based projects (e.g. MSBuild, legacy GNU Make, etc), VisualGDB creates a separate .vgdbsettings file for each configuration. For advanced project types, settings for all configurations are the same and are stored in the .vgdbproj or .vgdbcmake file.
That said, you can use the $(ConfigurationName) variable throughout VisualGDB Project Properties to distinguish debug/release configurations. Specifically, for Make-based ESP-IDF projects, you can set VisualGDB Project Properties -> ESP-IDF Project -> SDKConfig File to sdkconfig-$(ConfigurationName) (you would need to copy it manually) and VisualGDB will use it when configuring the project. We have updated the tutorial to reflect this.
You can double-check the file used by VisualGDB by searching the build log for “SDKCONFIG=”.
Custom build steps are indeed shared between the configurations as well, however you can work around it by using the “Reference a reusable action list” step that links to another file with steps. Simply link to a ExtraSteps-$(ConfigurationName).xml file, and VisualGDB will load 2 different files depending on the selected configuration.
Hi,
No problem, we can investigate this further. Please try updating to VisualGDB 5.6 Beta 5. If the problem persists, please try reproducing it on a clean project from scratch and sharing the repro steps we could follow on our side per our problem reporting guidelines.
Oh, thanks for pointing this out. We had the same issue with the RISC-V toolchain where our toolchain build passed the tests, but the official one did not.
Our latest ARM toolchain release has fully passed our internal tests with VisualGDB 5.6, so the Ninja executable shipped with it must include a workaround for it as well. In this case, updating to it should be a safe bet.
Hi,
This is a known bug of some of the Windows GCC builds: due to some reason, the paths inside the .dep files end up escaped incorrectly. We updated the VisualGDB itself (i.e. MSBuild) to handle the broken paths properly a while ago, but this won’t help with the external tools like Ninja.
Generally, please try using our latest ARM toolchain. It’s built from the official GNUARM sources using the official instructions (+flags enabling support for big-endian devices), and does not have the path encoding bug (we don’t know why the official release does).
You can also try replacing the Ninja executable in the VisualGDB directory with the latest release (or updating to VisualGDB 5.6 that includes a newer version), but this may not work either.
Hi,
According to our records, your support period has expired. Please kindly renew it here and we will help you get everything working.
Hi,
No problem. We normally wait until the toolchain is released via the Espressif’s toolchain installer (otherwise it often just doesn’t work due to missing files or compatibility issues), however this time it looks like due to some reason they didn’t update the installer despite releasing a fairly stable toolchain.
Either way, we have updated our ESP32 toolchain to include the 2021r1 tools and ESP-IDF 4.3.1, and verified that basic projects can be built and debugged. You can download the new toolchain via VisualGDB Package Manager, or directly here.
Hi,
Code Explorer has been introduced in VisualGDB 5.6 Beta 5. Please make sure you update to it, and it will appear automatically. You can also manually activate it via View->VisualGDB Code Explorer.
Hi,
VisualGDB 5.4 has been released over 2 years ago and is no longer maintained. In order to get the latest updates, we recommend updating to VisualGDB 5.6.
Hi,
This is something to check in the MSP430 GCC documentation. E.g. you may need to specify it to both compiler and linker, or to specify some additional settings.
You can also verify the exact flags passed by VisualGDB to GCC by reviewing the RSP files (MSBuild) or adding “-v” to Ninja command line (CMake).
Hi,
This looks like a generic programming issue and not something VisualGDB-specific. If you believe VisualGDB is not working as expected, please try reproducing the problem from scratch (on a cleanly created empty project) and let us know the steps to reproduce it per our problem reporting guidelines.
If the problem only happens on a specific project, please try comparing this project to a cleanly created project until you can pinpoint a specific setting that is causing this. If you believe this setting is not working as expected, please let us know more and we will investigate it further.
