{"id":27224,"date":"2020-01-23T22:37:22","date_gmt":"2020-01-23T21:37:22","guid":{"rendered":"https:\/\/sysprogs.com\/w\/?p=27224"},"modified":"2020-04-21T19:29:05","modified_gmt":"2020-04-21T18:29:05","slug":"announcing-visualgdb-5-5-preview-3","status":"publish","type":"post","link":"https:\/\/sysprogs.com\/w\/announcing-visualgdb-5-5-preview-3\/","title":{"rendered":"Announcing VisualGDB 5.5 Preview 3"},"content":{"rendered":"

Today we have released VisualGDB 5.5 Preview 3. This version features automatic repair of the most common C\/C++ build errors, supports unit tests for IAR- an ESP-IDF-based projects, and introduces numerous other improvements. I will give you an overview of the main highlights below.<\/p>\n

<\/p>\n

Automatic Symbol Search<\/h2>\n

One of the most annoying types errors for C\/C++ projects are the errors caused by missing headers or libraries. If you ever had to inetgrate 3rd-party code into your projects, you have likely spent some time resolving the infamous ‘foo’ was not declared in this scope<\/strong> error. VisualGDB 5.5 Preview 3 has the smarts to automate this process for you. Simply click on “Search common headers for <Symbol><\/strong>” next time the compiler complains about a missing symbol and let the search begin:\"\"<\/a>VisualGDB will automatically scan the headers in the project’s include directories (including the system headers and project-specific headers) and will use Clang IntelliSense to tell apart the actual declaration from comments, similar-looking fields inside structures, forward struct declarations and other false positives:\"\"<\/a>VisualGDB caches every symbol it finds during the symbol search, so once it gets a chance to look through the most common headers, the suggestions will appear immediately:\"\"<\/a><\/p>\n

The symbol search is not limited to finding header files. It will also help you troubleshoot the dreaded undefined reference to ‘bar’<\/strong> error via a tooltip in the new VisualGDB Build window:\"\"<\/a>Similarly to header search, VisualGDB will scan the nearby libraries for definitions<\/strong>\u00a0of the missing symbols and will let you pick the one that fits the best:\"\"<\/a><\/p>\n

Embedded Projects<\/h2>\n

The troubleshooting capabilities of the Preview 3 get supercharged if you are using it to develop embedded projects based on the recently released BSPs. Those BSPs come with special annotations that help VisualGDB discover missing configuration file entries, framework references, etc:\"\"<\/a><\/p>\n

This is especially useful for Nordic nRF5x projects where each component of the complex Bluetooth LE stack needs to be enabled independently via VisualGDB Project Properties:\"\"<\/a><\/p>\n

Talking about configuration files, VisualGDB 5.5 Preview 3 features a graphical editor for common entries in the STM32, FreeRTOS and nRF5x configuration files, so you can easily find and edit them in one place:\"\"<\/a><\/p>\n

Unit Test Improvements<\/h2>\n

VisualGDB 5.5 Preview 3 includes out-of-the-box support for ESP-IDF unit tests. You can now use Solution Explorer to add test cases to your components and then use the regular Test Explorer GUI to run or debug any subsets of tests at your choice:\"\"<\/a><\/p>\n

Preview 3 also supports simultaneous debugging of multiple STM32H7 cores, unit tests for IAR-based projects and contains numerous usability improvements and fixes.<\/p>\n

Try It Out<\/h2>\n

You can download VisualGDB 5.5 Preview 3\u00a0here<\/a>. Don\u2019t hesitate to\u00a0write to us<\/a>\u00a0if you have a feature suggestion, or encounter a bug. You can also browse the full VisualGDB change log\u00a0here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Today we have released VisualGDB 5.5 Preview 3. This version features automatic repair of the most common C\/C++ build errors, supports unit tests for IAR- an ESP-IDF-based projects, and introduces numerous other improvements. I will give you an overview of the main highlights below.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","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\/27224"}],"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=27224"}],"version-history":[{"count":8,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/posts\/27224\/revisions"}],"predecessor-version":[{"id":27241,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/posts\/27224\/revisions\/27241"}],"wp:attachment":[{"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/media?parent=27224"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/categories?post=27224"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/tags?post=27224"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}