Embedded Memory Explorer is one of the most loved Embedded features of VisualGDB. It helps you keep track of the FLASH and RAM used by your embedded project so you can be sure that your program fits into your device memory:The new VisualGDB 5.2 comes with a feature that makes this window even more efficient at finding out why is your program bigger than you wanted it to be. Continue reading The New Dependency View in Embedded Memory Explorer
One of the topics that got us a lot of feedback recently was the poor performance of the Visual Studio Memory window with embedded VisualGDB projects. Two main problems reported by our users were lack of memory view when the program is running and the fact that it tried reading a wider memory area that was actually displayed, sometimes causing the underlying tools to crash. We have solved that in VisualGDB 5.2 with a brand new Advanced Memory Window specifically designed for maximum usability with VisualGDB projects.
The new system for running C++ Unit Tests added to VisualGDB 5.2 has out-of-the-box support for CppUTest and GoogleTest framework. But it’s also designed to be easily extendable to support any other test framework through a flexible set of rules defined in XML files. This post will describe how the test frameworks are defined and what can be customized in the framework definitions to support more frameworks.
One of the new features introduced in VisualGDB 5.2 is the seamless integration of C++ unit testing frameworks into Visual Studio. VisualGDB supports the CppUTest and GoogleTest frameworks for Linux, Android and Embedded projects out-of-the-box and also comes with a powerful customization mechanism that allows describing any other test framework in a way that will allow VisualGDB to discover and run tests from it with just a few mouse clicks.
Let’s look into the new unit test system in detail.
Continue reading The New Unit Test Support in VisualGDB 5.2