[support]

Hi,

Do you mean that you would like to see the percentage of each section that is occupied by the actual symbols vs. padding at the end of the section?

[support]

Hi,

If the PreprocessorDefinitions macro gets resolved before the custom tool has a chance to run, please consider a slightly different approach. Remove the reference to your variable from the regular PreprocessorDefinitions and add the following code inside your <Target> element after the invocation of the custom tool (please update it to reference the actual variables):

<ItemDefinitionGroup>
 <ClCompile>
 <PreprocessorDefinitions>%(ClCompile.PreprocessorDefinitions);$(...)</PreprocessorDefinitions>
 </ClCompile>
</ItemDefinitionGroup>

As long as the code above is inside the “target” element, it will get evaluated after the tool is invoked and hence the variables will be resolved properly.

[support]

Hi,

Yes, the fix will be included. We currently plan to release another preview of v5.4 introducing a feature similar to CodeLens this week, then the first beta in another 1-2 weeks followed by a stable version in a few weeks more (depending on the feedback on Beta).

[support]

Hi,

VisualGDB 4.3 is very old and likely contains many bugs that have been fixed in later versions. Please consider updating to VisualGDB 5.4 Preview 7.

[support]

Hi,

Please double-check that your project is ARM-based and then check the Embedded Debug Tweaking page of VisualGDB Project Properties for the “ARM Semihosting” section. If it’s not shown, please attach  screenshots of the Embedded Debug Tweaking and MSBuild/Makefile Settings pages.

[support]

Hi,

The “cannot access a disposed object” error looks like a known VS bug. Please try installing the latest VS updated (not VisualGDB, but VS itself).

The wizard window looks like the VS theme was not loaded properly and VisualGDB could not get the correct colors. Reinstalling VisualGDB should normally help as it would trigger cache rebuilding. If not, please let us know which VS version you are using and also attach a screenshot of the main VS window and the “new project” window so we could see what parts of the theme are not loaded.

[support]

Hi,

Thanks for sharing this. Indeed the target name should not collide with any of the existing targets, as it would override the original target. Setting $(BuildDependsOn) to include your target name should be the right thing to do.

If it doesn’t work, please try setting the MSBuild build log verbosity to “Diagnostic” via Tools->Options->Build and Run and then check that your target is being built, the task is being executed and returns the correct value and that it happens before the actual compilation phase.

[support]

Hi,

Please try opening View->Embedded Memory Explorer and keeping it open in the detailed view. It will automatically update each time you build the project, showing you the detailed per-section and per-symbol statistics (and also other useful information like offline disassembly or stack usage analysis).

[support]

Hi,

Sorry, we haven’t tested kgdboe with this kernel version yet. We will run the tests on it, patch it and update the version installed by VisualKernel in the next few months.

If the fix is trivial and you don’t want to wait for an official update from us, you can simply fork our Github repo, patch the code and replace the files in %LOCALAPPDATA%\VisualGDB\VisualKernel\KernelPackages\kgdboe.

[support]

Hi,

Thanks for sharing this. We have just finished rechecking everything with the latest OpenCV release and the latest Raspberry Pi toolchain and updated the tutorial.

We have also added a few usability features to VisualGDB (e.g. automatic deployment of installed CMake targets), so please use this build if you would like to try the new features.

[support]

Hi,

The text you attached doesn’t contain any specific error message, so the problem may not be on the OpenOCD’s side.

Please describe what exactly you are observing/expecting and also obtain and attach a gdb session log as described here so that we could see what is going on.

[support]

Hi,

We would advise using VisualGDB. It will automatically handle symlinks when synchronizing the sysroot and will also upload the directories correctly when building projects.

[support]

Hi,

If you are using MSBuild, you can script it by creating a custom MSBuild target (VisualGDB uses the same target system as regular MSBuild projects).

You can find extensive documentation on creating MSBuild tasks here: https://docs.microsoft.com/en-us/visualstudio/msbuild/task-writing?view=vs-2017

Also consider having a quick look through our version updating task used by our open-source plugins. You could create a similar C# task that would export an MSBuild variable and then reference this variable in the “Preprocessor Definitions” setting.

 

[support]

Hi,

No problem, we will help you resolve it. VisualGDB 5.4 imports the custom toolchain by creating folder under %LOCALAPPDATA%\VisualGDB\ToolchainProfiles\localhost. Please double-check that a folder corresponding to your toolchain has been created and that it either contains a Toolchain.xml/CustomToolchain.xml file, or points to the toolchain directory via a ToolchainLink.txt file (in the latter case the toolchain directory itself should contain the XML file).

Then check the XML file for the toolchain type (i.e. that it’s set to “Linux”). You can also get a detailed debug log of the toolchain enumeration logic by enabling View->Other Windows->VisualGDB Diagnostics Console and then opening VisualGDB Package Manager (this will reload the toolchain list).

If nothing helps, please attach:

• The relevant screenshot showing no toolchain in v5.4
• The diagnostic log mentioned above
• Your Toolchain.xml or CustomToolchain.xml file and let us know where it was located (under %LOCALAPPDATA% or in the toolchain directory).

This should help us narrow it down and suggest a working solution.

[support]

Hi,

Most of the VisualGDB’s settings are stored in registry under HKEY_CURRENT_USER\Software\Sysprogs\VisualGDB\Settings, so you can delete the subkeys of this key (don’t delete the key itself, as it would break the license-related logic and make VisualGDB unusable on that machine).

The only subset of settings not affected by this is Tools->Options->Text Editor->C/C++ (VisualGDB)->General/Scroll Bars/Tabs as those settings are managed by Visual Studio itself. The easiest way to reset those 3 tabs is to simply copy the values from any other language (e.g. regular C/C++).

[Author]

Posts