Forum Replies Created
-
Posts
-
No problem, we have fixed the formatting of your post.
The clang code analysis output is indeed only shown for the current file. The main use case for it is to detect common errors as you write new code and suggest the fixes similar to the regular IntelliSense errors/warnings.
We do have long-term plans for scanning the entire project for warnings and showing an easy-to-use searchable report, however this won’t make it into v5.4 due to our release schedule constraints.
Hi,
No problem and good to know it works. VisualGDB doesn’t add the locations of all headers to the header search list as it would cause very hard-to-track errors with some libraries (e.g. the ones with separate private/public headers). We do support this for advanced mbed projects and MSBuild-based projects, but unfortunately we won’t be able to support this on Android projects as it might cause more problems than it would solve.
As for the upgrade, we have loaded VisualGDB 5.4 with support for many new platforms, redesigned GUI, better custom actions, advanced code navigation and other features that make it easier to use, but ultimately it’s up to you to decide whether the upgrade is worth it based on your project types and requirements. Feel free to contact our sales if you would like to get a trial extension voucher to try out the new version.
Hi,
Thanks, we have fixed the expanded list height in VisualGDB Project Properties in this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.100.2728.msi
Unfortunately we were not able to reproduce the second problem. Most likely it is caused by some specific properties of your .filters file. If you could share a basic repro project, we should be able to fix it.
VisualGDB uses the VS filters do distinguish between the files automatically added from the BSP (that will be overwritten next time you regenerate the files, change the MCU or update the BSP) and your project files that are not changed. Hence there is no option to disable them. You could try converting your project to a stand-alone one that doesn’t reference any files from the BSPs and reorganizing the sources manually.
In the next major version we are planning to support the advanced CMake project subsystem as the primary build system for embedded projects. VisualGDB will then fully control what is shown in Solution Explorer and will be able to provide a higher degree of customization.
Hi,
No problem. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.100.2728.msi
It will remember the last used host selected via the “Find” button and the “nostop” flag. You will be also able to add/remove the “,nostop” part manually just as before.
Hi,
This looks like a bug that was recently fixed in the Espressif’s OpenOCD implementation. We have updated our packages to include this fix.
Please try installing the latest ESP32 toolchain via VisualGDB Package Manager and (also install the “ESP32 Debug Methods” package or create a new project via the ESP32 project wizard). This should get the latest OpenOCD with the most recent fixes.
Hi,
No problem. We can help you get this to work.
When determining IntelliSense include paths, VisualGDB doesn’t use the GCC compiler path from the toolchain file. Instead it uses the path specified when importing the toolchain. You can configure it via VisualGDB Project Properties -> CMake project settings -> Toolchain -> (button with the wrench icon).
Then try closing the solution, deleting the ImplicitCompilerFlags.xml file from the VisualGDBCache directory and opening the VisualGDB Diagnostic Console.
Next time you open the project, VisualGDB will run the gcc from the toolchain definition with the flags reported by CMake and will detect the include directories based on that.
If this doesn’t help, please attach your ImplicitCompilerFlags.xml file, a screenshot of the toolchain definition and, the output from the diagnostics console and the CodeModel.json file from the VisualGDB\Debug directory and we will check what is going on.
Hi,
Do you use the “Find” button to find the target? If yes, we could make it remember the last state of the flags for each target.
Hi,
Please try updating to VisualGDB 5.4 Beta 2 and then right-click in Solution Explorer on an Arduino project. The “Add->Manage Arduino Boards” will be available there.
If it doesn’t appear, please share a screenshot and we will help you locate it.
Hi,
The code analyzers run together with IntelliSense error checking and display the results in the Errors pane (see this thread). If you believe it doesn’t work, please let us know more details (e.g. screenshots) and we will help you configure them.
Hi,
Thanks for updating your profile. However, it looks like your technical support period has expired a while ago.
Please consider updating it here: https://sysprogs.com/splm/mykey (the 50% discount will add 1 year to the original expiration period; alternatively please contact our sales for a 10% late renewal discount that will extend the expiration period to a year from now).
As soon as you renew your support, we will be happy to explain the semantics on $(LOCAL_PATH) and other Android-related settings.
Hi,
Depending on the mode you used for importing the project, the preprocessor macros might not have been imported automatically.
If you could attach your keil project file (no source files are necessary), the screenshots of all the steps of the VisualGDB import wizard and the macro name that is set in the Keil project and not automatically imported into VisualGDB, we should be able to tell what is going on and update our importer accordingly.
Hi,
No problem. Please let us know the email associated with your license key so that we can link it to your forum profile and we will be happy to help you.
Hi,
Please consider using the MSBuild Exec task instead. It should work regardless of the project type and other VisualGDB-related settings.
Hi,
Please try creating a temporary copy of the interface configuration file (e.g. esp32_devkitj_v1.cfg) and add the ftdi_serial command there (OpenOCD should show the serial numbers of connected devices if multiple matching adapters are found), then specify the copied script in the Debug Settings.
Normally VisualGDB should do this automatically, however we have not explicitly tested this with the ESP32 devices, so minor adjustments might be required. Feel free to let us know your observations and we should be able to update VisualGDB to do this automatically.
Hi,
Most likely the Keil project is using a different configuration file.
If you have 2 similar projects and would like to compare them, please consider enabling the preprocessor output in VisualGDB (VS Project Properties -> C/C++ -> Outputs) and Keil. This will expand all #include<> directives and the preprocessor macros, so you should be able to see where are various macros/variables defined and why the corresponding definition was not included in the other project.
