{"id":12487,"date":"2017-09-26T00:10:04","date_gmt":"2017-09-25T23:10:04","guid":{"rendered":"https:\/\/sysprogs.com\/w\/?p=12487"},"modified":"2017-09-26T01:05:47","modified_gmt":"2017-09-26T00:05:47","slug":"announcing-visualgdb-5-3-rc1","status":"publish","type":"post","link":"https:\/\/sysprogs.com\/w\/announcing-visualgdb-5-3-rc1\/","title":{"rendered":"Announcing VisualGDB 5.3 RC1"},"content":{"rendered":"

Today we are proud to announce the release of VisualGDB 5.3\u00a0Release Candidate 1. This version\u00a0introduces\u00a0profiling and code coverage support for Linux projects, Linux Dynamic Analysis, advanced code annotation and\u00a0a few other improvements. In this post I will\u00a0give you an overview of the new features:\"01-prof\"<\/a><\/p>\n

<\/p>\n

Linux Profiling<\/h2>\n

VisualGDB\u00a0is now fully integrated with Valgrind<\/a> –\u00a0a powerful Linux profiling tool. You can now easily\u00a0find\u00a0the critical paths of your program by simply selecting Analyze->Analyze Performance with VisualGDB:<\/p>\n

\"02-profgui\"<\/a><\/p>\n

Profiling Linux projects looks very similar to profiling Embedded projects – VisualGDB will run\u00a0the program under profiler and create detailed report files showing the amount of instructions executed within each function or line of code:<\/p>\n

\"03-tree\"<\/a><\/p>\n

If you are using Visual Studio 2013, 2015 or 2017, VisualGDB will show the\u00a0statistics like number of invocations, spent time and number of incoming\/outgoing calls on top of each function in your code:<\/p>\n

\"04-annotate\"<\/a><\/p>\n

This lets you easily explore the\u00a0real call tree (including the virtual methods) without waiting\u00a0for the entire source code to be\u00a0indexed:<\/p>\n

\"05-calls\"<\/a><\/p>\n

You can also enable per-line annotations and VisualGDB will show you how much time each line took to run and\u00a0which functions were called from that line:\"06-lines\"<\/a><\/p>\n

The profiler also tracks incoming calls, so you can see the list of all functions that called a certain function during the profiling session (even if this happens across multiple shared libraries):\"07-calls\"<\/a><\/p>\n

Then you can navigate the call tree to find the full call stack and\u00a0understand the context better.\u00a0VisualGDB\u00a0can distinguish invocations of the same\u00a0function from different\u00a0contexts and\u00a0will\u00a0show the times and callers lists accordingly:\"08-calledfrom\"<\/a><\/p>\n

If profiling the entire program run slows it down too much, VisualGDB lets you turn the profiling on and off dynamically. Start in the “Debug and get ready to profile” mode, then step to the critical part of your program and enable profiling. VisualGDB will handle the low-level Valgrind commands automatically and let you view the relevant results:
\n\"09-live\"<\/a><\/p>\n

Code Coverage<\/h2>\n

VisualGDB 5.3 RC1 also includes out-of-the-box support for code coverage.\u00a0Simply enable the “Generate\u00a0Code Coverage Reports” setting in your build settings and VisualGDB will automatically instrument your code for code coverage analysis with gcov:
\n\"01-instr\"<\/a><\/p>\n

Enable the “Build code coverage reports” option via VisualGDB Project Properties and VisualGDB will automatically locate, download and parse the coverage files\u00a0and present you with an easily searchable structured report:\"02-cov\"<\/a><\/p>\n

The coverage reports let you see detailed per-function statistics (in blocks and lines)\u00a0and can quickly highlight the\u00a0lines that were never executed during your test run so you can easily\u00a0modify your tests to cover them:<\/p>\n

\"03-covreport\"<\/a><\/p>\n

Dynamic Analysis<\/h2>\n

We have also added support for detecting\u00a0run-time memory and threading problems by using the Valgrind dynamic analysis tools. Simply enable dynamic analysis via\u00a0VisualGDB Project Properties and you\u00a0run your program under debugger:\"01-analyze\"<\/a>VisualGDB will automatically configure Valgrind to detect the selected type of issues and will show you details on each issue when it is detected:\"02-break\"<\/a><\/p>\n

 <\/p>\n

Embedded Memory Explorer Improvements<\/h2>\n

If you are using Visual Studio 2013 or later, VisualGDB will now display function sizes and stack usage (not\u00a0recursively yet), directly in the code as long as the Embedded Memory Explorer window is active and the detailed\u00a0view is enabled:\"01-stats\"<\/a><\/p>\n

It will also show the sizes and offsets of various struct members so you can\u00a0quickly troubleshoot\u00a0forgotten alignment attributes or unexpected sizes:\"02-eme\"<\/a><\/p>\n

All information is taken from the actual ELF file, so it will 100% match the\u00a0behavior of your program, even if the IntelliSense configuration has some settings incorrect.<\/p>\n

Other Small Improvements<\/h3>\n

We have added a few smaller improvements to various components of VisualGDB. E.g. Advanced CMake Projects\u00a0are now better integrated with TFS, automatic XMing launching is now more reliable and the toolchain selection GUI looks less confusing on high-contrast color schemes and the embedded chronometer will now display the time elapsed since last event directly in the code:<\/p>\n

\"chrono\"<\/a><\/p>\n

Try It Out<\/h2>\n

VisualGDB 5.3 RC1 is out. You can download it on this page<\/a> and don’t hesitate to send us your feedback via the support form<\/a> or forum <\/a>so that we can make VisualGDB even better.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Today we are proud to announce the release of VisualGDB 5.3\u00a0Release Candidate 1. This version\u00a0introduces\u00a0profiling and code coverage support for Linux projects, Linux Dynamic Analysis, advanced code annotation and\u00a0a few other improvements. In this post I will\u00a0give you an overview of the new features:<\/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":[422],"_links":{"self":[{"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/posts\/12487"}],"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=12487"}],"version-history":[{"count":5,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/posts\/12487\/revisions"}],"predecessor-version":[{"id":12509,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/posts\/12487\/revisions\/12509"}],"wp:attachment":[{"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/media?parent=12487"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/categories?post=12487"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/tags?post=12487"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}