[support]

Sorry, the “undefined reference” is not something specific to VisualGDB. It’s an error shown by the linker if the project does not include definitions (not declarations) of the referenced symbols. The best thing we can offer via our regular product support is the 2 tutorials linked above. They explain the differences between the definitions and declarations in detail. We would advise taking time to follow them and go through the diagnostic steps described there, as it will help you get a better understanding of the logic behind handling of references.

If you believe the issue is on the VisualGDB side, please try reproducing it from scratch (including creating a new project) and documenting every step. If you could share all the steps with the relevant screenshots, we can try to pinpoint the most likely cause of the issue.

We can also review your specific project and point out the locations of the declarations/definitions of the symbols, and adjust the settings to include all the necessary files, however as it’s something specific to the project, we would have to charge a consulting fee for it. Feel free to contact our sales if you would like to get a quote.

[support]

Hi,

The trial period is indeed 30 days. However, according to our records, it has previously expired. Please note that re-downloading/reinstalling VisualGDB does not restart the trial period.

[support]

Hi,

No problem, please see the following tutorial for a detailed explanation of the “undefined reference” errors: https://visualgdb.com/tutorials/linux/libraries/diagnosing/

There is also another one that explains a similar issue for the embedded projects: https://visualgdb.com/tutorials/tips/externc/

[support]

According to our records, your trial period has expired. If you would like to continue receiving support, we would kindly ask you to purchase a license. If your need more time to evaluate VisualGDB, please feel free to contact our sales from your corporate email address, and we will be happy to help you and your team get everything working in no time.

[support]

Hi,

No problem, we can help you. However, we would kindly ask you to confirm your support status first. Please let us know the email address associated with your license key and we will link it to your support profile.

[support]

Hi,

Sure, you can sue the regular Embedded Project Wizard to either create a basic “LEDBlink” project, or to clone one of the STM32CubeMX samples. This requires the regular Embedded Project Wizard (not the STM32CubeMX Project Wizard) and does not involve any external tools.

You can find more details in the following tutorial: https://visualgdb.com/tutorials/arm/stm32/

[support]

Hi,

Please try using VisualGDB Project Properties -> Embedded Debug Tweaking to enable saving of various output types to files.

If you would like to access the files on the Windows machine from the embedded targets, please consider using the Test Resource Manager API.

[support]

Hi,

Sorry, this is not supported. In order to keep compatibility with older Visual Studio versions, VisualGDB is using a legacy interface for managing the code outline. Although it supports all of the other functionality, it indeed does not show the structure guide lines. We will consider updating to the newer interfaces in one of the next VisualGDB releases.

[support]

Hi,

This might be related to a bug where VisualGDB would not pass the target selection flags to the IntelliSense engine. Please try this build: VisualGDB-5.6.1.4051.msi

If it doesn’t solve the problem, please try checking the CppEngineTuningInfo.xml file. It contains a list of rules for determining the target based on the preprocessor flags discovered from the project. Please let us know if your target is listed there and the flags shown in View->Clang IntelliSense Status->Project Structure match any of the targets defined in CppEngineTuningInfo.xml.

[support]

Hi,

The “Valgrind failed to initialize” error is shown when the diagnostics process (with the ‘cat’ command) would exit prematurely. Please try running the commands manually to reproduce the problem:

rm -rf /tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa
mkdir /tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa
mkdifo /tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa/valgrind.log
valgrind --log-file="/tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa/valgrind.log" --vgdb-prefix="/tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa" --tool=callgrind --callgrind-out-file="/tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa/callgrind.out" --vgdb=yes --vgdb-error=0 /tmp/CentralControllingApplication
cat "/tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa/valgrind.log"
vgdb --vgdb-prefix="/tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa" --port=2000

Then, check for any suspicious messages or strange behavior. Note that the last 3 commands will need to run in parallel from 3 different terminal windows.

If none of the commands exits, please try checking if running gdb (gdb <executable>) and connecting it to Valgrind (target remote :2000 followed by continue) works.

Please let us know your findings and we will help you configure VisualGDB to work with your setup as well.

[support]

The ‘\n’ behavior could vary between different C library versions and environments. Please see step 6 of the tutorial for an explanation.

[support]

Thanks for clarifying this. Most likely, you have skipped some other step of the tutorial then.

We can gladly help you recheck everything if you could share the exact steps you follow, from the very beginning to reproducing the problem, including all relevant screenshots. Please see our problem reporting guidelines for a very detailed example.

[support]

Hi,

Raspberry Pi is still supported, although the Git repository of the WiringPi library has indeed changed. We have updated our tutorial to reflect the new address.

The WiringPi tutorial indeed shows the older VisualGDB GUI, however the names and locations of the relevant settings have not changed. We do recommend using MSBuild instead of GNU Make though. Please double-check that you specify both include paths and library names per step 7 of the tutorial.

If nothing helps, please feel free to let us know more about the errors you get, including any relevant screenshots, and we will try to suggest a workaround.

[support]

@arrow201, thanks for pointing this out!

[support]

Hi,

No problem, please refer for the following page for a detailed explanation of the STM32 project structure: https://visualgdb.com/documentation/embedded/stm32/

[Author]

Posts