[support]

Hi,

Thanks, this might be related to a recently fixed bug. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.3.18.2008.msi

[support]

Hi,

That would normally count as a valid attempt to rename the function. If this is annoying, we could easily add an option to disable this behavior.

[support]

Hi,

The shortcut actually comes from Visual Studio.  You can see under in Edit->IntelliSense together with a other IntelliSense commands. If you are not familiar with Visual Studio commands and shortcuts, we would advise looking through the Edit menu – it contains a few very powerful commands.

[support]

Hi,

Sorry, unfortunately that is not directly supported. However as for CMake projects the Solution Explorer contents is dynamically built from the CMake project structure, you can simply copy-paste the CMakeLists.txt file structure to a newly created project (and also copy all relevant sources) and VisualGDB will automatically update Solution Explorer to show the contents of your project.

[support]

Hi,

Strange, normally this would not happen. Does this happen in the Output window (the regular Build Output pane?)? Could you please share a screenshot so that we could see if anything else could provide a hint to the cause behind this?

[support]

Hi,

You can achieve this by adding “-j<# of cores>” to the Make Command -> Customize -> Arguments. You can also use the $(LocalMultiThreadedBuildFlags) expression instead of “-j<#number>” to let VisualGDB automatically query the number of cores from your system properties.

[support]

Hi,

Stopping in “HardFault_Handler” usually a problem in the firmware you are trying to debug (e.g. trying to access an invalid memory location).

The most likely reason for this behavior is incorrect memory layout. You can easily diagnose this by creating map files both in Eclipse and VisualGDB and then comparing them (e.g. check locations/sizes of .text and .data sections, stack pointer/etc). If you get stuck, please try attaching both map files here and we will try to check them for common errors.

[support]

Hi,

This looks like the renaming smart tag that should normally appear when you rename a function declaration (it would let you automatically adjust the references). If it’s triggering on a function call, most likely you did not include the header file with the function declaration, so Clang treats your call as an implicit declaration. Please include the correct header file in your sources to fix this.

[support]

Hi,

Yes, please use Tools->VisualGDB->SSH Host Manager->Host-wide settings->Temporary directory.

[support]

Hi,

jsmith, thanks for the suggestion. We are actually experimenting with a custom project subsystem for the ESP-IDF projects that will basically map the internal ESP-IDF structure directly to Solution Explorer (similar to our Advanced CMake subsystem). Once we release it, it will let you use the original esp-idf while having VS-style look-and-feel. We cannot promise any specific deadlines for this yet, however we will likely release it in the first half of 2018.

[support]

Hi,

VisualGDB generates the gcc_Debug.h file during toolchain testing (it runs gcc with the arguments specified in your project properties and in a special mode where it dumps all implicit preprocessor macros). Most likely your project somehow explicitly overrides the ‘unix’ macro and VisualGDB doesn’t catch it.

You can resolve this by either editing the gcc_Debug.h file (it won’t be regenerated unless you edit some toolchain-related settings in VisualGDB GUI) or adding something like this to one of your commonly used header files:

#ifdef SYSPROGS_CODESENSE
#undef unix
#endif

[support]

Hi,

Unfortunately as you have cropped the screenshot, hiding the navigation bar, we are not able to tell whether the Clang engine is properly attached to the source file. Please attach a screenshot of the entire VS window as requested above.

Also if the manual auto-completion (triggered by Ctrl+Space) works, but the automatic one doesn’t, please try clicking the lightning symbol in the auto-completion popup to enable the automatic mode.

[support]

Hi,

VisualGDB 4.2 is more than 3 years old and is naturally missing many usability features. Please install the latest VisualGDB 5.3 – it allows excluding specific subdirectories using the ‘-‘ syntax, e.g.:

-.git;*

This syntax will recursively upload all files from all directories, automatically skipping over .git (and its subdirectories).

[support]

Hi,

This could happen if you were using the previous version of the STM32 BSP with the original GNU ARM toolchain (not the toolchain shipped by us). Please double-check that you have the latest version of the STM32 BSP.

[support]

Hi,

VisualGDB actually supports the original ESP-IDF projects using a slightly different mechanism (it is fully described here), so we would advise updating the IDF in the esp-idf.orig folder and trying it out.

The generator usually needs minor updates between ESP-IDF releases due to breaking changes. We are planning to update it (and also release an updated toolchain) within the next month.

[Author]

Posts