{"id":12552,"date":"2017-10-01T04:49:55","date_gmt":"2017-10-01T03:49:55","guid":{"rendered":"https:\/\/sysprogs.com\/w\/?p=12552"},"modified":"2017-10-01T04:49:55","modified_gmt":"2017-10-01T03:49:55","slug":"10-reasons-to-try-out-visualgdb-5-3","status":"publish","type":"post","link":"https:\/\/sysprogs.com\/w\/10-reasons-to-try-out-visualgdb-5-3\/","title":{"rendered":"10 reasons to try out VisualGDB 5.3"},"content":{"rendered":"

Today we\u00a0happy to announce the final release of VisualGDB 5.3. Over the past several months and\u00a08 preview builds we have introduced and fine-tuned multiple\u00a0usability-focused improvements to your cross-platform development workflow and I will give you a quick overview of them in this post.<\/p>\n

<\/p>\n

Advanced CMake Project Subsystem<\/h2>\n

VisualGDB has been supporting CMake for a while. However the new v5.3 brings this support to a new level. The new\u00a0Advanced CMake Project Subsystem\u00a0can be used\u00a0instead of the regular Visual C++ project system,\u00a0mapping the structure of the CMake files directly into Visual Studio: visualizing targets and settings and automatically editing CMakeLists.txt files in response to your\u00a0interaction with Visual Studio GUI:\"cmake\"<\/a><\/p>\n

Direct SSH file access<\/h2>\n

Previous versions of\u00a0VisualGDB could upload your source files to the Linux machine before building, or help you setup shared folders. The new VisualGDB 5.3\u00a0introduces\u00a0a new “vgdb-ssh:\/\/” file URL\u00a0 format and lets you\u00a0open, edit and build your projects directly on the Linux machine\u00a0over\u00a0SSH without importing anything locally:\"direct\"<\/a><\/p>\n

This\u00a0eliminates synchronization issues and makes setup straight-forward, although it only works with the new Advanced CMake Projects.<\/p>\n

Embedded\u00a0Debugging Usability<\/h2>\n

In VisualGDB 5.3 we have\u00a0significantly redesigned the usability of the embedded debug GUI. VisualGDB can now\u00a0distinguish individual instances of programming interfaces (like ST-Link) and\u00a0identify them\u00a0by serial numbers, will show progress when programming FLASH memory with OpenOCD and will diagnose common errors and show meaningful messages\u00a0helping you quickly understand the underlying problem:\"emb\"<\/a><\/p>\n

New Toolchain Engine<\/h2>\n

VisualGDB 5.3 includes a new toolchain\u00a0and BSP engine that\u00a0supports installing multiple\u00a0versions of the same\u00a0toolchain or BSP (Custom edition and higher),\u00a0provides convenient variables to avoid hardcoding toolchain\/BSP paths in the project files or VisualGDB settings files and makes the toolchain management generally more intuitive:\"tc\"<\/a><\/p>\n

Profiling of Linux Programs<\/h2>\n

VisualGDB 5.3\u00a0supports profiling of Linux programs using Valgrind and a powerful analytics engine built on top of it. Simply\u00a0start\u00a0profiling via Analyze->Analyze performance with VisualGDB and enjoy detailed instantly searchable per-function and per-line reports on your\u00a0code performance, or use them to explore the actual relations between functions involved in handling a complex case:\"06-lines\"<\/a><\/p>\n

Better integration with STM32CubeMX<\/h2>\n

In recognition of the growing popularity of the STM32 devices, VisualGDB now supports importing STM32CubeMX projects out-of-the-box. Simply point to a gpdsc file generated by STM32CubeMX and VisualGDB will\u00a0automatically\u00a0convert it into a\u00a0Visual Studio project and will automatically update it if the original gpdsc project changes:\"cubemx\"<\/a><\/p>\n

Static and dynamic code analysis<\/h2>\n

VisualGDB 5.3\u00a0also supports static code analysis powered by Clang and dynamic code analysis of Linux projects powered by Valgrind (Custom edition and higher).\u00a0\"02-break\"<\/a><\/p>\n

Embedded Integration Tests<\/h2>\n

If adding a unit test framework to your embedded project sounds like too much work, VisualGDB offers a much more\u00a0lightweight solution to\u00a0keep your code health in check. Simply use the debugger to alter your program behavior, record its responses and insert\u00a0checks\u00a0validating the return codes, function execution times and the order of events:\"progress\"<\/a><\/p>\n

Test coverage for Linux tests<\/h3>\n

VisualGDB 5.3 supports integration with gcov.\u00a0Simply\u00a0enable coverage instrumentation via VisualGDB Project Properties and you will be able to see detailed reports on covered functions, blocks and lines for both remotely built\u00a0projects and projects using a cross-compiler:\"03-covreport\"<\/a><\/p>\n

Team Settings Engine<\/h2>\n

If you ever\u00a0had to synchronize\u00a0VisualGDB settings like toolchain definitions\u00a0between multiple machines,\u00a0we have good news for you. The new Team Settings Engine lets you\u00a0instantly publish common settings to a\u00a0shared folder on your network and immediately make them available to other team members:\"toolchains\"<\/a><\/p>\n

This feature works on top of the\u00a0regular Windows file permissions and uses\u00a0intuitive XML files to store the shared settings, so you can check them in under source control and\u00a0track the changes.<\/p>\n

Bonus: Updated GUI<\/h3>\n

If you have tried VisualGDB 5.3 (or RC) before, don’t forget to update to\u00a0the final release. It includes numerous small improvements to\u00a0various components and better WPF-based versions of several common\u00a0user interfaces that had known issues on high-DPI screens:\"term\"<\/a><\/p>\n

You can find a detailed list of changes in the changelog<\/a>.<\/p>\n

Try it out<\/h2>\n

VisualGDB 5.3 is out.\u00a0Give it a try here<\/a> and don’t hesitate to\u00a0send us your feedback via the support page<\/a> or forum<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Today we\u00a0happy to announce the final release of VisualGDB 5.3. Over the past several months and\u00a08 preview builds we have introduced and fine-tuned multiple\u00a0usability-focused improvements to your cross-platform development workflow and I will give you a quick overview of them in this post.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/posts\/12552"}],"collection":[{"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/comments?post=12552"}],"version-history":[{"count":1,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/posts\/12552\/revisions"}],"predecessor-version":[{"id":12559,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/posts\/12552\/revisions\/12559"}],"wp:attachment":[{"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/media?parent=12552"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/categories?post=12552"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/tags?post=12552"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}