Forum Replies Created
-
Posts
-
Hi,
This looks like a message coming from the ESP32 OpenOCD port that is maintained by Espressif. Most likely, some changes to the project configuration are either incompatible with JTAG debugging, or trigger a bug in OpenOCD.
Our best advice would be to try erasing the FLASH memory via esptool.py and reverting the change that triggered it. If you need further help with this, please consider submitting a bug to the ESP32 OpenOCD repository on Github.
Hi,
Good to know you know what is going on. In general, it is hard to suggest anything specific for a complex project that was created by someone else and involves numerous external points of failure.
If you believe VisualGDB is not working as expected, please try reproducing the problem completely from scratch (i.e. from creating a new project) and sharing the repro steps per our problem reporting guidelines. If we are able to reproduce the issue on our side, and can confirm that it is caused by VisualGDB, we should be able to resolve it.
Sorry, unless we can reproduce the issue on our side, we will not be able to address it. We will keep an eye out for other users reporting similar behavior and will fix it as soon as we are able to reproduce it.
According to our records, your support has expired a while ago. Please kindly renew it via this page and try installing the latest VisualGDB 5.6 Beta 4. If the problem persists, please let us know and we will help you get it working.
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.
