[support]

Looks like you are setting a breakpoint in an inlined function that has multiple physical locations (one per each inlined instance). Setting a breakpoint there involves one physical breakpoint per each inlined instance, and based on the log, there are more than 10 of them (see line with the [ 3544 ms]  tag). Running out of hardware breakpoints is completely expected in this scenario.

[support]

Hi,

Please try creating a gdb log and searching for the -break-insert commands (or any other command containing the “break” word). It will show the exact breakpoints set by VisualGDB.

If you can find a specific breakpoint that you believe should not be there, please let us know and we will help you understand what brings it in.

[support]

Please note that we are not able to review specific projects or code snippets for errors. Our support is limited to issues when VisualGDB itself is not working as expected. It does not cover the issues where the code itself is not working, or the target device is not behaving as expected. Having different clock dividers or different optimization levels will affect function timing and can trigger bugs in the code. This is to be expected and VisualGDB will not be able to fix those bugs automatically.

Please note the we only provide support in English.

We also have to prioritize the reported issues by the ease of reproducing/fixing it and the amount of affected users. Given the amount of resources already spent on the thread we will not be able to investigate it any further, or provide any further replies unless the issue starts affecting other users. Sorry.

[support]

Please note that VisualGDB is a productivity extension to Visual Studio. It makes building and debugging projects easier, however it does not replace an actual software engineer. It cannot automatically write code based on a verbal description, or fix the code that does not work as expected.

Fixing code that does not work as expected requires an engineer to review the code, its context, specific MCU datasheet and the related board design, and likely to debug it on the hardware. This would require non-trivial time and would cost much more than we charge per license, hence we are not able to provide it as a part of our product support. If you would like an engineer to review your project and help you resolve issues with it, please consider hiring a 3rd-party consultant.

[support]

We do our best to avoid confusion. We show the expiration date in the Help->About VisualGDB window and if VisualGDB fails to activate due to an old key, it directs to the MyKey page that lists renewal/upgrade options and also allows downloading the older VisualGDB versions.

Edit: the poster below pointed out the confusion here, so we will try to clarify. Any version released while the update period was active should be able to activate. Preview builds of VisualGDB may activate even beyond that, however updating to the next stable release will require active renewal period at the time of that release.

[support]

No problem. Also please note that as you have used the 50% renewal discount, your previous support/update expiration date has been extended by 1 year, placing it at 49 days from now. If this was not intended, you can instead use the 10% late renewal discount that will place it to 1 year from now (please contact our sales if you need a link to pay the difference). Or you could do another 50% renewal any time (before or after expiration) to add another year to the current expiration date.

[support]

Thank you for your feedback. As it takes continuous effort on our side to keep VisualGDB up-to-date, and test it with the new devices, tools and frameworks, we have to limit free updates to 1 year since the license purchase, and ask for license renewal afterwards.

We try to be very explicit about our renewal policy. Our buy page mentions the 1-year period and the renewal page provides a link to the latest version that can run with your key if you do not want to renew the license. Due to the way the installer framework works, it can only verify the license key after VisualGDB has been installed and you load it in Visual Studio.

That said, you can always uninstall the new VisualGDB version and install back the old one without losing any settings.

[support]

No problem, we have updated VisualGDB to remember the custom hardware register definitions selected for mbed projects. Please try this build: VisualGDB-5.5.101.3866.msi

[support]

Based on what you have described, it looks like a specific code snippet is not working as expected. It looks like an issue with a specific piece of code, rather than a VisualGDB bug. Also, unfortunately, you have not provided sufficient context for us to understand what is going on.

If the same project behaves differently when built with the Keil IDE vs. VisualGDB, please consider following this tutorial to track down the changes.

If it doesn’t help and you believe VisualGDB is not working as expected, please provide us the steps we could follow on our side to reproduce the problem per our problem reporting guidelines and we will try to investigate it further.

[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.

[Author]

Posts