What's new with TotalView for HPC
Delivering safe, robust code requires tools that help identify potential issues early, fit cleanly into development environments, and minimize impact on delivery times. The new TotalView for HPC delivers unbeatable platform, language, and compiler support for C, C++, and mixed-language Python – C/C++ applications.
TotalView “What’s New” splash screen
In order to better promote new features in TotalView, a What’s New splash screen will be displayed after a new version of the product is installed. The dialog provides convenient information about the latest new features and links to learn more about them. The splash screen can easily be dismissed and not shown again until the next new release is installed. To view the What’s New dialog again, simply select the “What’s New in TotalView” menu item from the Help menu.
TotalView’s new “NextGen” UI officially supported
Starting with 2018.2, TotalView’s new user interface is now officially supported and no longer an Early Access feature. For existing TotalView users, the default UI is still the TotalView Classic UI, but the default can easily be changed by changing the preference on the Display tab in the Preferences dialog. For brand new TotalView users, the new UI will be displayed by default. New features continue to be added to the new UI. Your feedback helps prioritize what features from the Classic UI need to be added to the new UI. Please send email to email@example.com with your thoughts about the new UI and any feature requests.
CUDA debugging model and unified display improvements
With the 2018.2 release, TotalView improves on the ability to easily set action points within CUDA applications and applications that dynamically load shared libraries with dlopen. In either case, until the CUDA or shared library code is loaded, the information required for setting a breakpoint is not available to the debugger. To address this issue, TotalView 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 CUDA or shared library code is loaded at runtime. For more information, see Chapter 27, CUDA Debugging Model and Unified Display, in the TotalView for HPC User Guide.
New user interface improvements
TotalView’s new user interface, activated through the Display Preferences panel or using the -newUI command line option, continues to deliver new enhancements to 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 firstname.lastname@example.org
Display std::string value without diving
New with 2018.2, TotalView now displays the resulting string value of a std::string without having to dive on the string and view it in the Data window. The string is now displayed in tooltips, in the local variable pane, and other locations where you would expect the string value to be displayed.
QString type transformation
TotalView 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. TotalView now does it for you.
Manage single-stepper skip rules
TotalView 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 TotalView Reference Guide.
For more details please refer to the TotalView release notes.