[support]

Hi,

This could be related to an issue we previously noticed with the ARM toolchain. Older versions of it appeared to come with unoptimized builds of GDB, so they were very slow at loading the symbols. Our toolchain is a repackaged version of the ARM toolchain, so it would be affected by this as well.

We have just updated it using a clean optimized rebuild of the latest GDB 15.1. Feel free to update it via VisualGDB Package Manager.

[support]

Hi,

This is likely some race condition between loading the colors from VS settings and using the loaded colors to render the memory window contents. However, it is hard to say anything specific without the logs from the new build. The log from 6.0R3 doesn’t help because v6.0R3 does not have the logic for logging the memory window theme events.

You can try this build: VisualGDB-6.0.103.5202.msi. If it still produces strange errors, it could be an indication of something else going wrong (e.g. some common assemblies or cache being corrupt). You can try creating a new project from scratch and trying out the memory window with it. If it still fails with strange errors, please share more details (project type, exact steps to create it, uncropped screenshots of the VS window showing the error).

[support]

OK, thanks very much for pointing this out. It turns out, when we moved the regex to the XML file and extended it to handle the (WSL (…)) syntax, it ended up with a typo, that still passed the test cases by coincidence.

We have updated the regex to \(WSL(| \(.*\))\), covering both short and extended form.

Feel free to update to this build: VisualGDB-6.0.103.5202.msi

 

[support]

Hi,

It looks like your technical support period has expired.

We would be happy to help you, however we would kindly ask you to renew your technical support and install the latest VisualGDB 6.0R3 that includes the latest fixes and optimizations.

[support]

Hi,

The second IntelliSense popup looks like it’s coming from another VS extension. Most likely, it does not recognize VisualGDB, and tries to show its popup nonetheless. You can try disabling other VS extensions to see which one it is.

Another option would be to change the mechanism used by VisualGDB to display the suggestion popups (Tools->Options->Text Editor->C/C++(VisualGDB)->Advanced->Code Completion->Smart Suggestion List GUI). Some of the options there could interfere less with the other extension.

[support]

Hi,

Please make sure you can get it working outside VisualGDB first. Once it is working, feel free to share the details about your setup, and we will point you to the relevant VisualGDB documentation.

[support]

No problem. This could be a bug that gets occasionally triggered under some conditions, although we would need more information to pinpoint it. Normally, the window should look like this on the dark theme:

We have slightly simplified the theme loading logic in VisualGDB and added extra logging to it. Please try this build: VisualGDB-6.0.103.5201.msi

If the problem persists, please follow the steps below:

1. Start a debug session.
2. Open and enable View->Other Windows->VisualGDB Diagnostics Console.
3. Open a memory window that was not open before (e.g. Memory 2). You can also try closing and reopening it.
4. Check the diagnostic log for messages mentioning Memory editor.

If you could post the exact messages you get along with the exact action that triggers them (e.g. opening a memory window for the first time), we should be able to narrow it down.

 

Attachments:

You must be logged in to view attached files.

[support]

Hi,

Thanks, this looks like the device type auto-detection wasn’t working due to another change in the SDK structure, although selecting it manually would still work.

We have fixed it in this build: VisualGDB-6.0.103.5201.msi.

 

[support]

Hi,

We have not specifically tested VisualGDB with this board. However, if it comes with a functional toolchain and the gdb debugger (i.e. you can build and debug a project manually), you can easily point VisualGDB to the same tools and let it drive building and debugging for you,

[support]

Hi,

This would normally only happen if you change the VS color theme after using the memory window for the first time. If this is the case, please try simply restarting Visual Studio, and the colors should look normal next time.

[support]

Hi,

Sorry, not sure what you meant. If you believe VisualGDB is not working correctly, please provide complete screenshots showing every step of the wizard, and every other step you take (e.g. changed settings), including the final error message you get. Please ensure the screenshots are complete and uncropped. A single error message taken out of context is often not enough to suggest anything meaningful.

[support]

Hi,

No problem, we have reproduced and fixed the issue. Please try this build: VisualGDB-6.0.103.5197.msi

[support]

Hi,

Thanks, looks like the U5 port is using a couple of built-in functions that are not known to Clang and somehow trigger strange behavior.

We have added a workaround on the VisualGDB side. Please try this build: VisualGDB-6.0.103.5197.msi

[support]

Hi,

Sure, it should work just fine. Just make sure you are using the latest VisualGDB 6.0R3 and selecting the ST fork of OpenOCD.

[support]

Hi,

Thanks, we have reproduced and fixed the problem. Please try this build: VisualGDB-6.0.103.5196.msi

[Author]

Posts