[support]

Hi,

No problem, we have added a command to toggle the CodeJumps annotations via Edit->Advanced menu to this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2552.msi

You can assign a keyboard shortcut to it via the Tools->Customize->Keyboard command.

Regarding the references, it indeed looks like some glitch on our side, however unfortunately we were not able to reproduce it on our side. Please try narrowing down a specific sequence of steps that leads to it, or simply capture a video demonstrating the problem. This should help us see what is going on and add a fix for this.

[support]

Hi,

Strange. We have rechecked all the assemblies shipped with VisualGDB and could not find any mixed-mode ones.

The error looks like the .Net runtime is failing to load the VisualGDB settings types. Could it be a corrupt .Net installation? Can you confirm that VisualGDB runs as expected on other machines in the same domain/with the same group policy?

We have also added extra logging to this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2552.msi

 

Please try reproducing the problem with it (enable verbose mode by adding “/v” to VisualGDB’s arguments). It should show a much more detailed exception report that should help narrow this down.

 

[support]

Hi,

Thanks for the detailed problem description and the screenshot. Looks like it was indeed a remnant from Cygwin-based toolchains on our side.

Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2552.msi

[support]

Hi,

No problem. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2552.msi

[support]

Hi,

Sorry, there isn’t any special command for renaming projects. You can use the VisualGDB template mechanism for some project types (e.g. MSBuild), but otherwise you would need to rename the project manually and update the following files:

• The .vgdbsettings files should be renamed to match the new project name.
• Any explicit references to the .vgdbsettings files inside the .vcxproj file should be updated.

That should be sufficient to get the renamed project to work. Let us know if you encounter any problems and we will help.

[support]

Hi,

OK, thanks for checking this. If updating doesn’t help, there might be a system setting that is blocking the VisualGDB.exe assembly, or the problem is caused by a different assembly.

Please try running the build command line shown in the log manually:

"C:\Program Files (x86)\Sysprogs\VisualGDB\\VisualGDB.exe" /build C:\Code\Linux2015\igc.nisttime.git_linked\igc.nisttime.git_linked\igc.nisttime.git_linked.vcxproj /solution:C:\Code\Linux2015\igc.nisttime.git_linked\igc.nisttime.git_linked.sln  /config:Release /platform:Win32

Do you get the same error? If yes, does running VisualGDB.exe without arguments also result in the same behavior? If no, please try setting the “VISUALGDB_VERBOSE_OUTPUT” environment variable in a command line prompt and running the full build command line again. This should produce a more detailed error log.

Another option would be to try adding the <startup> element to the .config file as shown in this thread: https://stackoverflow.com/questions/6425707/mixed-mode-assembly-is-built-against-version-v2-0-50727-of-the-runtime

[support]

Hi,

Thanks for renewing your license! It looks like your forum email was different from the email used in your order, so our system was not automatically picking up the latest key. We have linked them together now in our system.

Regarding the error, it looks like you are using an older VisualGDB version that does not include a configuration file listing all compatible .Net runtimes. This can be fixed via one of the following options:

• Updating to VisualGDB 5.4 Preview 8.
• Downloading the attached .config file and placing it in the same directory as VisualGDB.exe.
• Installing the .Net 2.0 runtime via Control Panel -> Add/Remove Programs.

Let us know if you encounter any further problems and we will be happy to help.

Attachments:

You must be logged in to view attached files.

[support]

Hi,

We could issue you a trial extension voucher so you could check if the latest VisualGDB 5.4 resolves the problem, but unfortunately we are not able to offer any personalized technical support unless the support period is renewed.

[support]

Hi,

Thanks for contacting us. According to our records, your support period has expired. In order to keep on receiving technical support, please renew your license or let us know the email associated with your new license key.

[support]

Hi,

The estimated time is just a linear extrapolation based on the average speed so far. If the remaining time is going up, the parsing speed must be consistently going down. It could be caused by running out of RAM, or slow disk performance. Please let us know the total/free RAM shown in Task Manager when the cache is rebuilding.

The cache is invalidated either when some of the build options (e.g. preprocessor macros) change, or when some of the files get outdated. The v5.4R8 build will show the exact reason for cache invalidation in the Clang IntelliSense Diagnostics Console (search for “invalidating cache chunk” messages).

[support]

Hi,

If you have tight time constraints, please consider trying Segger J-Link. It is more expensive than other debug probes, but comes with its own fully supported replacement to OpenOCD that works out-of-the-box with many devices. VisualGDB supports both Segger J-Link and OpenOCD, so you can choose the underlying tool based on your requirements.

[support]

Hi,

You can disable the code annotations by clicking the wrench symbol at the bottom right corner of the popup to open the options window, and then disabling annotations for all C/C++ entity types.

The “updating global symbol cache” is shown when VisualGDB is doing a global search (e.g. finding a definition, or all references). The remaining time should be shown after the progress advances a bit. If it never completes, please let us know if the progress is changing at all and if all the CPU cores on your machine are in use. If not, it might be stuck somewhere and we can help you pinpoint and fix it.

[support]

Hi,

If debugging consistently works on one project and consistently doesn’t work on another one, we would advise making a list of differences between the 2 projects and eliminating them one-by-one to see which one causes the problem.

If turning on external RAM indeed interferes with debugging, please inquire with Espressif for possible workarounds.

[support]

Hi,

No problem, we can add a workaround to the first problem that will automatically restart CMake if it crashes during reconfiguration.

The second problem looks like you are using backward slashes in the path to GNU Make (configured via VisualGDB Project Properties). Please try using forward slashes instead and let us know if this solves the problem.

[support]

Hi,

VisualGDB uses the general “Stale Code” setting from Visual Studio Options (Text Editor -> Fonts and Colors).

[Author]

Posts