[support]

Hi,

We actually have a detailed tutorial showing how to import 3rd-party Linux projects build with command line: https://visualgdb.com/tutorials/linux/import/ (it features an older VisualGDB version though).

Please try following it and let us know if you encounter any problems.

 

[support]

Hi,

This indeed looks strange. Please try saving and deleting the following registry key:

Computer\HKEY_CURRENT_USER\Software\Sysprogs\VisualGDB\Settings\CppEngine

It should reset VisualGDB settings related to code formatting & indentations.

[support]

Hi,

OK, there are actually 3 different preprocessor macros related to the standard:

• __cplusplus
• __cpp_attributes
• __STDC_ISO_10646__

Please double-check that you are actually comparing the values of the same macro between the actual IntelliSense, IntelliSense.props and the gcc output. Also if you are using the Visual C++ IntelliSense (not Clang), it will set its own value of __cplusplus and modifying it would break IntelliSense (as it would include code paths using features that are not implemented by the VC++ IntelliSense).

Please also attach a screenshot showing the incorrect IntelliSense behavior, so we could check if it could be caused by anything else.

 

[support]

Hi,

This could happen if the gdb stub you are using did not report the registers correctly or if VisualGDB did not parse them properly (our plugin for Segger J-Link had a bug with the registers, but it got fixed years ago). Please let us know which gdb stub you are using and also attach:

• A screenshot of the registers window with the right-click menu
• Your VisualGDB version and build number
• The full GDB log from the debug session as described here

Thanks.

[support]

Hi,

Please try running the following command manually in the GDB session window:

dump binary memory <file> <start address> <end address>

[support]

Hi,

Please try using #ifdef DEBUG.

[support]

Hi,

Most likely some of your headers defines #unix if it detects GCC/clang being used.
Please try checking this on a clean project and/or using ‘go to definition’ on the ‘unix’ macro to locate where it is defined.

[support]

Hi,

Please try right-clicking there and selecting the register groups you need.

[support]

Hi,

If you are using a Custom edition or higher, you can simply add a custom pre-build action.

Another option would be to add a custom Makefile target or a cutsom MSBuild target. We don’t have an example specific to protobuf, however you can try following our tutorial for building Qt projects with MSBuild for a detailed example on creating custom MSBuild rules and targets.

[support]

Hi,

You could have a look at our open-source BSP generators. However please note that they come with absolutely no support of any kind. Newer SDK releases often include breaking changes that stop the BSP generators from working. We usually address them when we release the updated BSP, however we cannot provide any support if you want to try doing this before we start supporting that SDK officially.

[support]

Hi,

This looks pretty strange. Perhaps some code above is confusing VisualGDB? Can you reproduce the same behavior in an empty file? If not, could you reduce the problem to a specific statement above the cursor that causes this?

[support]

Hi,

For MSBuild projects VisualGDB stores the IntelliSense configuration in the following file:

%LOCALAPPDATA%\VisualGDB\ToolchainProfiles\<remote machine>\<toolchain ID>\IntelliSense.props

Please check the conditional definitions for the C++ standard you are using, e.g.:

<ItemGroup>
    <ClCompile Condition="'%(ClCompile.CPPLanguageStandard)' == 'CPP11'">
        <PreprocessorDefinitions>%(ClCompile.PreprocessorDefinitions);__cpp_attributes=200809;__cpp_static_assert=200410;__cpp_variadic_templates=200704;__GXX_EXPERIMENTAL_CXX0X__=1;__cpp_delegating_constructors=200604;__STDC_UTF_16__=1;__cpp_raw_strings=200710;__STRICT_ANSI__=1;__cplusplus=201103L;__cpp_ref_qualifiers=200710;__cpp_rvalue_references=200610;__cpp_rvalue_reference=200610;__cpp_nsdmi=200809;__cpp_initializer_lists=200806;__cpp_lambdas=200907;__cpp_unicode_characters=200704;__cpp_unicode_literals=200710;__cpp_range_based_for=200907;__cpp_decltype=200707;__cpp_inheriting_constructors=200802;__GNUC_STDC_INLINE__=1;__STDC_UTF_32__=1;__cpp_alias_templates=200704;__cpp_constexpr=200704;__cpp_user_defined_literals=200809</PreprocessorDefinitions>
    </ClCompile>
</ItemGroup>

You can also try deleting the file and re-opening the project. VisualGDB will then run the remote gcc and re-detect the preprocessor macros.

[support]

Hi,

Most likely your baud rate in SmarTTY settings doesn’t match the baud rate of the device. Most ESP8266 boards have the default baud rate of 74880 and most USB-to-UART adapters have a default rate of 115200. Please try setting the baud rate manually.

[support]

Hi,

Good to know it works. BTW, if you miss any other features of the Custom edition, you can always upgrade here: http://sysprogs.com/splm/mykey.

[support]

Hi,

Normally the output from the ESP8266/ESP32 programs is directed to a serial port, so in order to see it you would need to use the raw terminal feature (requires the Custom edition or higher). If you are using a lower edition, please try using our free SmarTTY tool instead to view the output from the COM port.

[Author]

Posts