Forum Replies Created
-
Posts
-
This feature is scheduled after the integration with the CMake server, so we would expect a preview build with this feature early this Summer.
It is based on a completely different technology than the embedded profiler, so many of the functionality will be different. Our best advice would be to wait for the first preview build with this feature and then send us your feedback if you find anything to be counter-intuitive or inefficient.
Hi,
Thanks for the explanation. As Intel Edison is not as popular as Raspberry Pi and other modern boards, we don’t ship a separate toolchain for it (the only other option would be to build a custom toolchain under our toolchain building service that usually costs EUR 1000 per toolchain).
Some GCC toolchains are configured in a way that requires their location to be stored in the registry, so just extracting the files for such a toolchain won’t work. We would recommend checking the archives and 3rd-party sites for a usable toolchain; if the toolchain itself is broken and does not work, VisualGDB unfortunately cannot fix this.
Hi,
Sorry, this is not supported yet, although we are researching Valgrind support and will be adding some level of integration with it into VisualGDB 5.3.
Hi,
Sorry, translating our GUI to multiple languages would drive the VisualGDB price sky high, so we have to stick with English-only interface.
We are gradually switching the GUI over. Each new release has a few more dialogs and settings pages converted, so it gets better each time you update.
Hi,
Thanks, the session does not look out of the ordinary indeed. One last advice would be to try setting Advanced GDB Settings -> Startup and Exit -> When the debug session is ending -> Explicitly kill the process. This should force gdb to explicitly terminate the target process when exiting.
Hi,
The custom post-debug steps are only supported on the Custom edition of VisualGDB and higher (see the feature matrix). If you have purchased a lower edition, this feature would not be available.
You can always upgrade your edition at https://sysprogs.com/splm/mykey.
Another alternative would be to try understanding why gdb is not terminated properly. Please try enabling GDB logging via VisualGDB Project Properties and check the last gdb command that gets executed before GDB hangs.
Hi,
Thanks for reporting this, we have fixed the missing “additional linker inputs” handling in this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.16.1483.msi
The behavior with additional linker inputs is by design as both library names and additional linker inputs are saved in the same field in the QT project file. As names with spaces are generally not supported very well by GNU tools, VisualGDB does not support them either (you can still use them by editing the Qt project file manually, but VisualGDB GUI won’t show it correctly).
Hi,
Please contact our support with the details of your license key and we will help you resolve this.
Hi,
No problem, this should help us diagnose it quickly. Please contact us via the support form on our website to arrange the shipping.
Hi,
It looks like a bug introduced by the MinGW path translation. If you have the full msys, setting USE_DEL_TO_CLEAN to 0 should be the easiest fix.
Hi,
You can check for __GNUC__ or other GCC macros.
