[support]

Hi,

Sorry, this does not look like a VisualGDB-related bug. Normally it should not touch anything unless you go beyond the run-as-admin stage. This could be caused by some sort of a VS registry corruption or a corrupt installation. We would recommend trying to move away VS-related folders in your user account and restarting Visual Studio to recreate those folders.

[support]

Hi,

Thanks, it’s a known issue. This happens due to limitations of the WinForms technology used by VisualGDB to show GUI. We are gradually switching our GUI to the newer WPF technology that should resolve this.

We have also received feedback that WinForms GUI looks better on high resolution displays after installing the Windows 10 Creators Update.

[support]

This could happen if the other file is not a part of the project. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.16.1466.msi

It should print the lookup progress to the window available via View->Clang IntelliSense Diagnostics Console.

[support]

Hi,

We usually respond faster to issues that do not require thorough investigation (like crash dumps). We will follow up on the crash dumps once we have more information about the cause.

[support]

Hi,

Thanks, looks like a toolchain bug. Can you reproduce this with the command-line ESP-IDF environment as well?

[support]

Hi,

Thanks, actually looks like our bug. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.16.1464.msi

[support]

Hi,

Good to know it works. BTW, VisualGDB should be able to install even if the VS is installed to a custom directory. So we would really appreciate it if you could let us know the details on your previous installation parameters so that we could reproduce it and ensure VisualGDB would detect it properly.

[support]

Hi,

Sorry, no specific plans yet. The main problem is that most Arduino users expect the development tools to be free and hence would not be interested in buying a VisualGDB license. We may eventually add basic experimental support and see if it gets any traction, but currently we are prioritizing other features over it, sorry.

[support]

Hi,

The LIB_SSH2_SCP_PROTOCOL error usually happens when the file access permissions on the Linux side are insufficient to either download or upload the file. Please check the permissions on the file mentioned in the error message. If you are not sure, please let us know the full error message and we will advise you on further diagnostic steps.

[support]

Hi,

Are you installing the latest VisualGDB 5.2R9? Does Visual Studio 2017 appear in the VS version list in VisualGDB installer when you click “custom install”?

If yes, please try check if the C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions\Sysprogs\VisualGDB folder exists and if Visual Studio reports any errors via ActivityLog.xml when running devenv.exe /LOG.

[support]

Hi,

Thanks, looks like our bug. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.16.1462.msi

[support]

Hi,

Thanks, this actually looks like a side effect of one of our fixes on top of the original Clang. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.16.1462.msi

[support]

Hi,

It’s hard to say why the paths would be reported incorrectly without seeing the original build output. Please try running the build command manually via command line (outside VisualGDB) and check the paths reported there. If you are not sure, feel free to post the log here and we will help you find the correct settings.

[support]

Hi,

Hard so say what could cause that, but good to know it works. If you encounter the problem again, feel free to reopen this topic.

[support]

Thanks, we will check it out and release an updated toolchain within the next month.

[Author]

Posts