[support]

Hi,

Thanks for the detailed description. Most likely this is caused by some invisible characters near the line breaks that are interpreted differently by VS and by Clang.

If you ever get this problem again, you might be able to reduce it as follows:

• Add a line “void testfunc();” at the beginning of the source file (after #include-s)
• Replace each of the problematic line contents (without touching the area near the ending of the line) with a call to testfunc().
• Confirm that the problem persists.
• Delete all lines between the declaration of testfunc() and the problematic lines, and also all lines after it
• Remove references to your #include-d files.

If the problem can be still reproduced after reducing it to the test code, simply send us the repro file and we will check for the characters causing it and should be able to add a workaround.

[support]

Hi,

Yes, please try right-clicking on the project in Solution Explorer and select “Reload Project”.

[support]

Hi,

That is specific to ESP-IDF projects; until you build it for the first time, it will be missing the configuration header, so IntelliSense will show random errors and will fail to understand valid code constructs, hence VisualGDB shows a warning. Just building the project for the first time should get rid of this.

[support]

Hi,

This looks like a problem on the Windows side (the Linux target doesn’t need to access the Windows paths). Please double-check your file permissions or try using a different Windows folder for the project.

[support]

Hi,

Thanks for pointing this out – it turned out to be a bug introduced by the recently added Keil/RTX integration.

Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.10.2587.msi

[support]

Hi,

Please try updating to Preview 10. It includes a few fixes to the Arduino logic.

[support]

Hi,

It looks like VisualGDB loses synchronization between the source file contents in the VS editor and the contents as seen by the Clang engine.

Could you please check if closing the source file and reopening it solve the problem? Also is it specific to a certain source file, or does it occur randomly across the entire code base?

 

[support]

Hi,

Thanks for sharing this. We have added an option to the Linker properties under the VS properties for this setting to our development branch. It will be included in the upcoming VisualGDB beta.

[support]

Hi,

This error means that the remote file is either missing, or inaccessible. Please double-check that it exists by running the “stat <path>” command via SSH.

If the file is indeed missing, please try building the project first.

[support]

Hi,

Yes, VisualGDB can view the ESP32 hardware registers with J-Link, however this is not fully integrated into the Arduino workflow yet.

We have made it easier in this build though: http://sysprogs.com/files/tmp/VisualGDB-5.4.10.2586.msi

Please download our regular ESP32 toolchain and then point the hardware register viewer at the <SysGCC>\esp32\esp32-bsp\registers.xml file. This will import the register definitions from the regular ESP32 toolchain into your Arduino project.

[support]

Hi,

Are you looking into running hardware-specific tests in a simulator (fully supporting the emulation of the STM32 hardware), or are trying to run high-level tests that do not have any hardware dependencies?

[support]

Hi,

Thanks for the suggestion. We will research this and try to support CTest in the next major VisualGDB release (after v5.4).

[support]

Hi,

Sorry about that and thanks for sharing the 100% repro steps. Looks like VisualGDB was not unescaping some arguments properly. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.10.2583.msi

[support]

Hi,

Sorry about that, looks like our bug (we did not compensate for the fact that –login resets the working directory). We have updated the logic for wrapping the Cygwin commands in this build and tested it in several scenarios, so it should finally work: http://sysprogs.com/files/tmp/VisualGDB-5.4.10.2583.msi

Please open the toolchain editing window and manually set the command launch mode to “Interactive Bash Session”.

[support]

Hi,

Unfortunately it’s hard to suggest anything specific without knowing more details, so we would advise looking through the following pages:

• https://visualgdb.com/tutorials/tips/externc/ – tutorial explaining how to diagnose “Undefined symbol” errors
• http://visualgdb.com/support/linkerinputs/ – overview of various types of linker inputs

If this doesn’t help, please share more details about the exact errors you get and we will suggest further troubleshooting steps.

[Author]

Posts