[support]

Thanks for the log file. It looks like some combination of settings is preventing VisualGDB from showing some of the tool windows before updating its state.

We have added more diagnostic logging to this build: VisualGDB-5.4.110.3226.msi

Please try reproducing the problem with it and send us the updated log from the VisualGDB Diagnostics Console.

[support]

Hi,

The Additional Memories page should normally work, so most likely you are using some combination of settings that triggers a bug on our side. If you could reproduce this on a “LEDBlink” project created from scratch and send us the related files (ensure you clean the project before packing it), we should be able to release a hotfix for this promptly.

[support]

Hi,

Sorry about that, it looks like a known issue of the Windows installer triggered by broken dependencies between products.

As a workaround, please try running the following tool from Microsoft that can automatically repair the installation database: https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed

[support]

The Visual Watch and Live Variables windows are still using the older WinForms technology (other windows have been converted to WPF) and hence they indeed may look distorted on the high-DPI displays. We are planning to convert them to WPF in the next major VisualGDB release. That said, it should not affect any functionality, i.e. simply double-click underneath the header and start entering variable name. The watch item will be created as expected despite the incorrectly looking header.

[support]

Thanks, this looks like something GUI-related (the actual error is “Invoke/BeginInvoke cannot be called” shown on the screenshot).

Please try using View->Other Windows->VisualGDB Diagnostics Console to narrow this down. I.e. enable debug logging, reproduce the problem and share the diagnostic output from the diagnostic console.

[support]

Please ensure your project is built with semihosting support via VisualGDB Project Properties -> Embedded Project Properties -> Implementations for syscalls -> With Semihosting.

[support]

Hi,

This is a limitation of the WinForms grid used by the Live Variables control. The Expression column will automatically fit the space remaining after all other columns. Please try resizing the other columns instead and the Expression column will get automatically adjusted.

[support]

This is by design. VisualGDB automatically enables its windows depending on the type of the debug session that is started, however they are shown in the background.

As a workaround, please configure you session to have the Live Variables window in the foreground and the other windows in the background. Next time you start a debug session, Visual Studio will preserve that layout. All extra debug windows will open in the background.

[support]

It’s hard to say what is going on as the log you attached is truncated. Please try using the latest build here: VisualGDB-5.4.110.3225.msi

Then enable diagnostic logs as shown here: http://visualgdb.com/support/logsubmit

Then please attach a screenshot of the error message and the full diagnostic log produced by VisualGDB and we help you get it to work.

[support]

Most likely, the strcpy() function was built without the debugging symbols (e.g. it was originally written in assembly language) and hence stepping into it won’t work.

You can double-check this by running the “bt” command in the GDB Session window. If it doesn’t show a valid source location for the top frame, the function does not have debugging symbols.

You can step over the functions by using the Step Over command instead of Step In (i.e. F10 instead of F11). If the ‘frame not in module’ error happens when pressing F10, this could be caused by an exception inside the function itself (e.g. trying to copy from/to an invalid address).

[support]

Thanks for linking your license email to your forum email. According to our records, your license has an active maintenance period, so you can simply download and install the latest VisualGDB version from the download page and it will automatically pick up your existing license information.

[support]

The types of projects that VisualGDB can create come directly from the Tiva SDK. If the SDK does not contain certain libraries or APIs, there is no easy way to create a project based on it unless you are prepared to port it from another platform. Please feel free to double-check with TI support whether they provide CMSIS project templates for Tiva devices.

[support]

Thanks for renewing your support!

We have uploaded a repackaged version of the latest toolchain with the master ESP-IDF checkout here: http://sysprogs.com/getfile/525/esp32-gcc8.2.0.exe

Simply run the installer and VisualGDB will recognize the new toolchain automatically, although the CMake-based projects will not work due to a bug in the current master branch of ESP-IDF.

[support]

Hi,

We have just discovered your post in the “other tools” forum and moved it here. To get faster support for VisualGDB-related issues, please create topics in the VisualGDB forum.

Please follow our Tiva tutorial to create a Tiva project with VisualGDB.

 

[support]

Hi,

Last time we checked, the new toolchain was not compatible with any stable ESP-IDF releases (using both 3.2 and 3.3 results in build errors).

We do not advise using pre-release ESP-IDF checkouts due to relatively low reliability and hence will not officially release a toolchain based on one until it reaches a stable state.

If you would like to experiment with this at your own risk, we can help you configure VisualGDB to recognize the new toolchain, however you would need to renew your technical support first. Please also note that the new ESP-IDF/toolchain might be broken in some ways that would make debugging, or other functionality impossible and we cannot guarantee that it will work as expected.

Update: we confirm that the new toolchain works with the master ESP-IDF branch when imported into VisualGDB, however it only works when using GNU Make. CMake support is currently broken.Our previous advice regarding ESP-IDF branches still holds – please avoid using the pre-release branches unless you are prepared to troubleshoot complicated issues.

• This reply was modified 6 years ago by support.

[Author]

Posts