[support]

OK, strange. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.0.581.msi

Open the Clang IntelliSense diagnostics console, clear it, type the opening brace and observe the console output. Does it mention anything about the event being suppressed?

We have also added a fallback mechanism that should fix the indentation even if the auto-pairing did not get invoked.

[support]

Hi,

We have recently released a new toolchain containing an improved ESP8266 port of OpenOCD. We recommend using it for new projects instead of the unsupported xt-ocd tool.

[support]

OK, we have released a new ESP8266 toolchain that includes the newest SDKs and an improved OpenOCD port. You can update to it via Tools->Embedded Tools Manager.

A detailed tutorial on the new OpenOCD port is available here: http://visualgdb.com/tutorials/esp8266/openocd/

[support]

Hi,

We will look into this and release an updated package within the next few weeks.

[support]

Pedley,

Please check under Tools->SSH Host Manager->Host-wide settings->raspberrypi->Additional environment.

You may have redefined LD_LIBRARY_PATH there (it would automatically get defined there if your Raspberry Pi had it set in .bashrc before).

[support]

Hi,

As a workaround you can edit the Makefile settings by editing debug.mak and release.mak directly.

As VS IntelliSense often stops parsing the files silently when it encounters some extension that it does not support and those problems are very hard to diagnose, we recommend using the Clang engine instead.

[support]

Hi,

Thanks, that explains it. The Clang IntelliSense updates the bracket indentation when it sees both the opening and the closing bracket. By default when you type ‘{‘, the IntelliSense automatically inserts the ‘}’ and formats both of them according to your settings. Looks like you have disabled this feature via Tools->Options->Text Editor->C/C++ (VisualGDB)->Advanced->Typing Assist->Auto-match brackets.

We recommend enabling it back to get better formatting. We have also added a fix to the upcoming v5.1 version that will automatically un-indent the braces when bracket matching is disabled. Let us know if you want to try a pre-release build with this fix.

[support]

Hi All,

We have added support for Embedded Quick Debug to the v5.1 branch of VisualGDB. You can now quickly debug arbitrary embedded code without creating a project for it.
​You can try a pre-release build here: http://sysprogs.com/files/tmp/VisualGDB-5.1.0.579.msi

Note that it will upgrade the Quick Debug presets you open to a new format that won’t work with v5.0, so please make a backup of the %LOCALAPPDATA%\VisualGDB\QuickDebugPresets folder before trying it out.

[support]

Hi,

The brace formatting is controlled by a Visual Studio setting under Tools->Options->Text Editor->C/C++->Formatting->Indentation->Indent Braces:

Please double-check that it’s not enabled for you. If it is disabled, but VisualGDB still formats the code incorrectly, please let us know which version of Visual Studio you are using so that we could suggest further diagnostic steps.

[support]

Hi,

We recently fixed the global “Enable Clang IntelliSense by default” so that it applies to the running session as well.

Perhaps we are talking about different windows. Could you attach a screenshot of the window that pops up for you? We should be able to advise you how to disable it then.

[support]

OK, then we will update the parser so that the next version of our nRF51 package contains the correct definitions. Please also feel free to attach your patched XML file here so that everybody could download it before we release the next version.

[support]

Hi,

We don’t do that because in many cases the machine with the previous VisualGDB installation is inaccessible. But we do respond quickly if you request an activation reset via our support channels.

[support]

Hi,

Please add the include paths via VisualGDB Project Properties -> Makefile Settings -> Include Directories.

This will configure both IntelliSense and your compiler correctly.

[support]

Hi,

Normally when you change something on the Makefile Settings page and click “Apply” VisualGDB should retest the settings and update IntelliSense. Did this not happen when you changed the toolchain? Does it retest correctly when you change, let’s say, CFLAGS?

We’ll add an option to select the language directly in the wizard in the next version of VisualGDB. We will also see if we can make the Program Output to be the default output after debugging.

[support]

Hi,

Could you try replacing the contents of the main source file with the following:

#include <stdio.h>
#include <stdlib.h>

int main()
{
    printf(">%s<\n", getenv("LD_LIBRARY_PATH"));
}

Does it show the correct LD_LIBRARY_PATH when you debug it from VisualGDB?

[Author]

Posts