[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.

[support]

Hi,

For custom build, VisualGDB would actually expect you to configure IntelliSense manually. Hence manually editing the gcc_Debug.h file would be the recommended option.

If it does not help, please try using the ‘Go to definition’ command to locate the macro definition. Also please double-check that you are using the Clang IntelliSense engine and not the native VS one.

[support]

Hi,

Thanks for reporting this, we have fixed it in this build: VisualGDB-5.2.16.1459.msi

[support]

OK, thanks. We should be able to reproduce and fix it in v5.3. We will post an update here once we have a preview build with this feature.

[support]

Hi,

This could be indeed related.

We are actually planning to improve the large directory downloading in VisualGDB 5.3 and will reinvestigate this when adding the new feature. As a temporary workaround, please either try running VS as administrator, or temporarily remove the symlink during synchronization.

[support]

Hi,

If it only occurs once every few months, it’s probably easier to just ignore it rather than to try locating the cause. If it starts occurring more often after some specific change, let us know and we will try reproducing it on our side.

[support]

Hi,

Yes, you can experiment with the default Windows path for relative paths via VisualGDB Project Properties -> Path Mapping.

[support]

Hi,

The Clang IntelliSense caches the old file paths in the global file table in order to speed up the up-to-date check operations. The message can be safely ignored, but you can also simply remove the CodeDB directory to discard the IntelliSense cache.

[Author]

Posts