[support]

Hi,

Please refer to the following page for an overview of IntelliSense engines and settings: https://visualgdb.com/documentation/intellisense/

[support]

Sorry, we have tried reproducing this issue, but could not get the behavior you described. Please make sure you update to the latest VisualGDB 5.5 and also try disabling other Visual Studio extensions.

If this doesn’t help, please try reproducing it on a clean project created from scratch and share the steps we could follow on our side to reproduce the issue (see our problem reporting guidelines).

[support]

Hi,

Unfortunately, we were not able to reproduce the problem based on the description you provided.

If VisualGDB behaves differently than you expect, please share the steps to reproduce the problem per our problem reporting guidelines and we will try to investigate this further.

[support]

Hi,

Most likely, you have selected an incompatible combination of settings at some point. Unfortunately, it’s hard to suggest anything specific without knowing the exact setting you changed that started triggering the issue.

Hence, our best advice would be to reset Arduino Settings, delete all Arduino packages and create the project from scratch. You can find more details in our recently updated Arduino documentation.

If you believe that editing a specific settings has unintended consequences, please share the steps we could follow to reproduce the problem on our side (see our problem reporting guidelines) and we will try to investigate it further.

You can also find more information on observing the project output on the following documentation page: https://visualgdb.com/documentation/projects/arduino/#output

[support]

Hi,

Sorry, VisualGDB does not have any special support for nginx modules. Please try following generic instructions for building nginx modules and then try importing the project into VisualGDB.

[support]

Thanks for the suggestion. This is in our roadmap, however as it involves changes beyond a trivial change of IDs, it has a relatively low priority. We should be able to add this feature next time we update the device selection GUI, or if other users request it as well.

[support]

Sorry, VisualGDB uses the gdb debugger to debug the code, while Ozone uses its own debugging engine. If the specific project produces an image that breaks gdb, it is outside of VisualGDB’s control to fix this, as it relies on gdb internally. The only workaround we can suggest would be to try a different Keil/GDB version.

[support]

No problem. It looks like the gdb debugger is not able to properly report the source location of the breakpoint event:

*stopped,reason="breakpoint-hit",disp="keep",bkptno="1",frame={addr="0x08013366",func="main",args=[],arch="armv3m"},thread-id="1",stopped-threads="all"

This sometimes happens due to a bug in the Keil compiler that produces invalid DWARF debug symbols and typically affects code in a specific file beyond a certain line. As a workaround, please consider using the GCC compiler, or try splitting the source file into multiple smaller files. You can also experiment with setting breakpoints in different files to see if there is any pattern.

[support]

Sorry, not sure what the question was. In the last post in the thread you mentioned that both frequencies work now.

If you have any other questions, please feel free to repeat them here and we will do our best to answer them.

[support]

It looks like you are setting breakpoints in one project and are trying to debug another one. Based on the gdb log, the breakpoint is set in the following file:

C:/Users/dlp/source/repos/MbedProject_testCDC/mbed-os/targets/TARGET_STM/TARGET_STM32L0/TARGET_STM32L072xZ/TARGET_DISCO_L072CZ_LRWAN1/system_clock.c

The -file-list-exec-source-files command reports a different file:

C:/Users/dlp/source/repos/MbedProject_LoRa/mbed-os/targets/TARGET_STM/TARGET_STM32L0/TARGET_STM32L072xZ/TARGET_DISCO_L072CZ_LRWAN1/system_clock.c

Please double-check your settings and make sure you debug the correct project.

[support]

Hi,

Please make sure your build the project before debugging. If it doesn’t help, please attach the gdb session log here and we will check what is going on.

[support]

Hi,

This looks like something is seriously wrong with the debug settings. Please try re-creating the project from scratch by following one of our tutorials.

If it still doesn’t work, please share the screenshots of all the wizard steps you follow and any settings you change (per our problem reporting guidelines) and we will point out the step that is most likely to cause it.

[support]

Hi,

Thanks for reporting this. We are aware of the issue and have already fixed it in our development branch. However, as it does not affect any other part of the program than the About window, we will not make a separate hotfix for this, and will instead include it in the next major update.

[support]

Yes, please use the download page to download the latest version: https://visualgdb.com/download/

[support]

Thanks, we have confirmed the issue. Indeed, the synchronization link in the wizard was not working as expected with this toolchain (the button in VisualGDB Project properties did).

Please try the following build: VisualGDB-5.5.101.3850.msi

[Author]

Posts