[support]

Hi,

No problem. Although this is not documented yet, VisualGDB exports a public interface for reading the coverage report files. You can try it out as shown below:

1. Create a new C# project and reference the VisualGDBCore.dll assembly.
2. Create an instance of the CoverageReportReader class. Pass the path to the report file as the first argument, and null as the second one.
3. Use the AllFunctions property to get information for all functions.
4. Call the GetFunctionsInPotentiallyMatchingFiles() method with the name of a source file to get detailed line-by-line coverage information.

You can use Visual Studio’s IntelliSense and Go-to-Definition command to see the properties and methods of the CoverageReportReader class.

[support]

Good to know it works. Most likely, the files are downloaded because the paths reported by gdb don’t match the paths expected by VisualGDB. This would happen if the target had symbolic links in some directories.

You can troubleshoot it by checking the GDB Session window for the path reported by GDB and then setting a mapping via VisualGDB Project Properties -> Path Mapping.

[support]

Thanks for checking this. Most likely, the problem happens because VisualGDB fails to create a temporary terminal (pseudo-tty) to avoid mixing the output from the program with the output from gdb.

The easiest way to work around it would be to use gdbserver on the target (you can configure it by selecting the “gdb stub” mode in the VisualGDB Project Properties -> Debug Settings). This will eliminate the need to create a virtual terminal and should work around the problem.

[support]

Hi,

Strange. Just to double-check, are you able to run the program under gdb manually? I.e.:

gdb /mnt/TrollSystems/_Applications/ConTroll21_S6K2/ConTroll21_S6K2_Lin.exe
b main
run

If yes, does it change if you run it as “gdb –interpreter mi <path”> instead of just “gdb <path”> and use the “-exec-run” command instead of “run”?

[support]

Hi,

Please refer to the following page for detailed overview of VisualGDB’s IntelliSense engines and instructions for switching them: https://visualgdb.com/documentation/intellisense/

[support]

Sorry, this looks like something specific to the particular mbed project/board and not to VisualGDB, and hence is not under our control. Please consider the following resources for help on issues that are not specific to VisualGDB:

• Mbed forums to discuss issues specific to mbed
• StackOverflow for generic programming questions

Also if you can confirm that the problem does not happen when using a command-line debugger (e.g. gdb), but happens with VisualGDB, we can help you understand the differences and configure VisualGDB to match the command line gdb behavior.

[support]

Thanks for confirming your license status. We have linked your forum account to the new key.

We have also updated the VisualGDBExtensibilityExamples repository to reference the correct assembly out-of-the-box.

• This reply was modified 5 years, 5 months ago by support.

[support]

Hi,

Please try deleting the %LOCALAPPDATA%\VisualGDB\Python* folders, updating to VisualGDB 5.5 Preview 4 and then install Python 3.x via the VisualGDB Project Wizard. This will get the correct version of Python with pre-installed mbed scripts.

[support]

No problem, please try this build: VisualGDB-5.5.4.3567.msi It will remember the imported toolchain correctly.

The toolchain test failure is by design, as VisualGDB tries to run the program produced by the toolchain locally. For cross-toolchains, please select “Build under Linux over network”, pick the LXSS distro there and set the deployment target, so that VisualGDB can verify that it can run the result of a test build. Or simply ignore the error and proceed with the current setup, since it shouldn’t interfere with anything else.

[support]

Hi,

Looks like the second project is based on GNU Make and hence does not support property sheets. You can find a detailed overview of various project types here: https://visualgdb.com/documentation/projects/overview/

Normally, you can convert Make-based projects to MSBuild via the context menu in Solution Explorer, however this process is not 100% precise and may require manual troubleshooting afterwards.

[support]

Sorry, we are not able to review custom projects or board schematics as a part of our product support. If you would like to have your project reviewed via our paid consulting service, please contact our sales to get a quote.

[support]

No problem, we have updated the ESP32-WROOM tutorial, pointing to the Advanced ESP-IDF tutorial.

If you cannot get the wiring to work, please consider using a board that includes a ready-to-use JTAG programmer, e.g. ESP32-WROVER.

[support]

Hi,

Please make sure you use the Advanced ESP-IDF Project Wizard instead of the regular Embedded wizard: https://visualgdb.com/tutorials/esp32/esp-idf/

[support]

Just wanted to share an updated that we have published detailed documentation on MSBuild property sheets with VisualGDB projects here: https://visualgdb.com/documentation/projects/msbuild/propertysheets/

[support]

Hi,

Unfortunately, it looks like your support period has expired a while ago. Please renew it here and we will be happy to help you.

[Author]

Posts