Forum Replies Created
-
Posts
-
Hi,
No problem. In the long term, we will add support for collecting non-critical warnings during the project import, and showing them at the end of the import, however for now, invalid paths will be just ignored.
Placing the project in a correct location should indeed get it imported correctly.
Hi,
No problem, please try this build: VisualGDB-5.6.5.4312.msi
Hi,
Thanks, it looks like the .ewp file references some sources and include directories outside its directory, that resulted in some invalid paths when the project file was moved to a shorter path.
We have updated VisualGDB to skip over invalid paths rather than throwing an exception: VisualGDB-5.6.5.4312.msi.
That said, the project will likely not build until the missing files are manually located and added to it.
Hi,
This could explain it. If the custom target provider would cause the test host process to crash unexpectedly, VisualGDB would indeed display this message.
Our best advice would be to try attaching to the TestHost.exe executable and checking for exceptions. You can also try showing a message box with the current PID from the constructor of your target provider to make attaching easier.
Hi,
According to our records, your support period has expired a while ago. We can gladly point you to the relevant documentation, however we would kindly ask you to renew your support first.
Hi,
No problem, please let us know the email associated with your license key so that we could link it to your profile, and we will help you get it working.
If you are using the latest VisualGDB version, something is likely interfering with the VisualGDB internals. Please make sure you use an unmodified VisualGDB installation. If the problem persists, please try installing it on a different computer.
Hi,
Sorry, we have tried reproducing this on the latest VisualGDB build, but it worked just fine.
Please try updating to the latest VisualGDB 5.6 Beta 4. If the problem persists, please try changing your tab settings (e.g. tab size = 4, keep tabs) and let us know if this changes the behavior.
Also please try disabling all other VS extensions. One of them might be interfering with the VisualGDB’s code formatting logic.
Hi,
We generally prioritize feature requests based on the number of affected users. As this is a very specific request affecting a very small number of users, and can be achieved by implementing a custom visualizer, it has a very low priority and will likely not be added anytime soon.
If your company holds multiple VisualGDB licenses, please let us know the email associated with your key, and we will assign a higher priority to this.
Hi,
It looks like the .ewp file structure is slightly different from what VisualGDB expects, so the importing logic fails. If you could attach the .ewp file (please put it into a .zip archive), we can gladly investigate it and fix the importer.
If you do not wish to share the project file, you can also fork and update the IAR importing plugin directly.
The TrueStudio import should work out-of-the-box, as long as you select it in the wizard. If not, please let us know more details and we will look further into it.
Hi,
No problem. Please try uploading the zip file with the entire project to a file sharing service (e.g. OneDrive/DropBox) and posting a link here.
Hi,
We normally support the toolchains that are available as stable releases from Espressif. I.e. once a toolchain is available via the ESP-IDF tool installer, we recheck it on our side, make sure that the VisualGDB GUI is fully compatible with it, bundle it with the matching ESP-IDF version that we tested, and re-release it as a ready-to-use VisualGDB package.
Currently, the latest ESP-IDF installer (v2.10) still installs the esp-2020r3-8.4.0 toolchain, that matches our latest toolchain (esp32-gcc8.4.0-r3.exe).
Once the new toolchain is released by Espressif as a stable binary package, and is made available via the ESP-IDF installer, feel free to get back to us, and we will give you a timeframe on repackaging it as a VisualGDB package.
If you would like to experiment with pre-release versions of the toolchains, you can do it by simply building them manually and replacing the binaries inside c:\SysGCC\esp32 (the versions and paths are stored in the Toolchain.xml file), however it is something to do at your own risk.
Hi,
Thanks for sharing this. The exact FPU macros also depend on the selected CPU/FPU type, so the logic for detecting them based on the “-mfloat-abi” option alone indeed won’t be 100% accurate. That said, it only affects IntelliSense and will not cause any behavioral issues in the code. Editing the file IntelliSense.props file manually (or adding the extra IntelliSense flags options via VisualGDB Project Properties -> IntelliSense Settings) should indeed work around it.
Also, please consider switching to the new Advanced CMake Embedded Project subsystem. It uses a different mechanism for configuring IntelliSense that is not prone to this issue.
Hi,
If the issue is present with the default settings, it’s likely caused by some special characters in the source files. Please try reproducing it on a new project created from scratch, and then try attaching a .zip file with the entire project here, so that we could try reproducing it on our side.
