What's new with CodeDynamics
CodeDynamics looks at your complex C and C++ applications at execution time to help identify and correct bugs, memory issues, and crashes. Learn what's new in the latest release.
CodeDynamics 2018.2
User interface improvements
The CodeDynamics user interface has several great enhancements that make debugging your applications even easier. If you have any feedback about the new user interface, requests for new or missing features, or any problems please send email to tv-beta@roguewave.com
Display std::string value without diving
New with 2018.2, CodeDynamics now displays the resulting string value of a std::string without having to dive on the string and view it in the Data view. The string is now displayed in tooltips, in the VAR local variable pane, and other locations where you would expect the string value to be displayed.
QString type transformation
CodeDynamics 2018.2 automatically transforms instances of type QString in Qt 4 and Qt 5 applications. You are no longer required to locate and manipulate the underlying character data to a human-friendly format. CodeDynamics now does it for you.
Shared library unified display improvements
With the 2018.2 release, CodeDynamics improves on the ability to easily set action points within applications that dynamically load shared libraries with dlopen. In this case, until the shared library code is loaded, the information required for setting a breakpoint is not available to the debugger. To address this issue, CodeDynamics now allows setting a breakpoint on any line in the Source View, whether or not it can identify executable code for that line. The breakpoint becomes either a pending breakpoint or a sliding breakpoint until the shared library code is loaded at runtime.
Manage single-stepper skip rules
CodeDynamics now provides the ability to define single-stepper “skip” rules that modify the way source-level single stepping works. These rules identify functions that you are not interested in debugging. Skip rules can be defined to skip over a function or through a function. In skip over cases, the debugger does not step into the function, but rather over it. These are useful for skipping over library functions such as C++ STL code. Skip through rules tell the debugger to ignore any source-line information for the function, so that single stepping does not stop at source lines within the function. If the function being skipped through calls another function, that call is handled according to the original single-stepping operation. Skip through is most useful for callback or thunk functions. For more information and examples, see documentation for the dskip command in the CodeDynamics Reference Guide.
For more details please refer to the CodeDynamics release notes.