Forum Replies Created
-
Posts
-
Hi,
GCC and Keil compilers are indeed not 100% compatible, so switching your project to a different compiler might require non-trivial adjustments. We only recommend using Keil with VisualGDB if you are trying to build existing Keil-specific code. For all other cases we recommend using our GCC-based toolchain that is fully supported by all project types and works out-of-the-box.
Hi,
You can set the linker script via the MSBuild Settings page of VisualGDB Project Properties (the last setting on that page).
Hi,
Please use the “Signals & Exceptions” button in the GDB Session window. It allows overriding which of the signals are passed to the program.
Please note that disabling stops on SIGINT may stop breakpoints in your program from working, as they internally rely on catching this signal.
Hi,
Thanks for confirming this. Most likely the template was created from a stand-alone project and hence all projects created from this template will also be stand-alone.
You can turn semihosting off for stand-alone projects by manually editing the LDFLAGS, although the exact options to add or remove depend on the toolchain version you are using, although it might be non-trivial to find the right combination of flags. Normally we would advise re-creating the template from a non-standalone project. Then VisualGDB will let you conveniently change all settings via simple GUI menus for all projects created from this template (it will also automatically update the settings when you upgrade to a newer toolchain).
Also normally you don’t need to disable the semihosting – as long as your code doesn’t call printf() and other similar functions, the semihosting-related functionality will be automatically excluded from the project by the linker.
Hi,
Thanks for clarifying this. We have double-checked the advanced CMake projects with yocto-based toolchains and it indeed looks like VisualGDB might ignore the environment file for some of the tests.
Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2062.msi
Hi,
Thanks for clarifying this. The project structure of the VS cross-platform projects is different from the Win32 projects, so simply adding the VisualGDB platform to them would unfortunately produce unpredictable results.
We would advise importing the project using the VisualGDB project wizard. This will re-create the project file with all the necessary constructs and will discover and add the source files from the project directory.
Hi,
Sorry for the confusion. If you want to be able to easily migrate between the toolchains and BSP versions, please don’t convert your projects to stand-alone ones. The regular VisualGDB projects don’t hardcode any toolchain-specific (or BSP-specific) flags, so you can easily switch BSPs, toolchains, FP modes and other settings for them. The stand-alone projects are specifically designed for the case where you don’t want to rely on VisualGDB to manage your settings and want to be able to tweak them manually.
If you used the stand-alone projects due to a different reason, please feel free to share your constraints and we will try to suggest a better way of satisfying them without losing the convenience of the regular non-stand-alone projects.
Hi,
Thanks for confirming this. Then it looks like the project file itself is missing some of the elements the normal .vcxproj files should have. The easiest way to pinpoint this would be to use a diffing tool (e.g. KDiff3) to compare the 2 .vcxproj files side-by-side and try editing one of them to make it as close as possible to the other one. Once you encounter the step that causes this problem, you should be able to revert it on the other project to fix it.
Hi,
Strange. Could you please try creating a new MSBuild-based VisualGDB Linux project from scratch and confirm that the problem still persists? If yes, what are the contents of the C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Platforms\VisualGDB folder?
Hi,
Thanks for the linker command line. It looks like a project created with an older version of the toolchain that didn’t support disabling semihosting yet. In order to be able to fully remove semihosting code from the project, please re-create it with our latest ARM toolchain based on GCC 7.2.0.
Hi,
This looks like CMake doesn’t report some of the target information to VisualGDB. This is to be expected, as unit tests projects are not officially supported for Advanced CMake yet. That said, we might be able to investigate/fix this if you could create a basic repro project and send it to us (or attach it here).
Hi,
Thanks for the update. Normally the VisualGDB platform should be installed to the following path:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Platforms\VisualGDB
Please double-check that this directory exists. If it doesn’t, please double-check that the VS installation path in registry is correct:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\SxS\VS7\15.0
Below is an example of a correct value:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\
If you change the VS path in the registry, please uninstall and reinstall VisualGDB so that it can pick up the updated path.
Hi,
Strange. Another option would be to uninstall VisualGDB, repair the VS installation via the VS Installer, and install VisualGDB back. If this still doesn’t help, please let us know which Visual Studio version you are using and where is it installed and we will provide more detailed steps on diagnosing MSBuild-related files.
Hi,
Looks like there is some sort of a configuration problem. If you are using the Advanced CMake Project Subsystem, it should not create any .props files and the project file extension should be .vgdbcmake, not .vcxproj. If you are not sure, please attach the screenshots of Solution Explorer and the first page of the wizard when you create a project and we will help you understand what is going on.
