[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, 6 months ago by support.

[support]

Hi,

This is actually a bug introduced by the new “Optimize rendering for screens with different pixel densities” setting in VS2019, that prevents the tool windows based on the WinForms technology from being shown correctly. We have added a workaround for this in the following build: VisualGDB-5.4.109.3224.msi

Please let us know if it doesn’t solve the problem.

[support]

The ESP-IDF framework is indeed very complicated and may not always work out-of-the-box. Generally, if you believe that a certain version of ESP-IDF doesn’t work at all, please request help on the ESP32 forum. On the other hand, if the framework works as expected (e.g. the project builds successfully via command line), but VisualGDB does not work together with it, we should be able to fix it as long as you are using an official ESP-IDF release and can provide sufficient details for us to reproduce the problem.

[support]

Yes, please send it to us via our support form.

[support]

Normally, unless you change a specific project-level setting (e.g. add another sketch file), the project itself doesn’t need to be checked out, so based on what you have described, this looks OK.

[support]

Hi,

Please try using the Debug-only preprocessor macros field on the first page of VisualGDB Project Properties (ensure you are using the latest VisualGDB version).

[support]

This is by design. The Arduino build system prioritizes simplicity over flexibility and hence automatically finds libraries by scanning the main header file for missing includes and then resolving them to the libraries.

[support]

Please let us know the email associated with your key (or update the forum profile accordingly) and we will let you know the latest VisualGDB version that can work with it.

[Author]

Posts