compared with
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (7)

View Page History
h1. Baseline Set of Debuggers
h1. Debuggers

Date of Policy: 1st November 2011
First Update: 23rd September 2011
Second Update: ???
Second Update: 20th February 2012

The lack of a baseline set of debuggers can compound what is arguably one of the most difficult tasks in scientific code development -- debugging new algorithms. The process of tracking down bugs in large scientific codes is frustrating and time consuming. Having to learn a new tool to do so limits efficiency and productivity of valuable HPC programmers.

For these reasons, a baseline set of debuggers preferred to be installed at all centers has been identified by examining what is in use at different centers and what can be used across a variety of platforms. At this time, only two three packages are included in the baseline set:

|| Debugger Name || Description || Compliance Level || References ||
| Totalview | A long standing de-facto standard for debugging in the HPC realm offered by TotalView technologies. \\ TotalView requires purchasing a commercial software license to be used | SHOULD | [] |

In order to be compliant, a center must have at least the first of these debuggers installed and in the standard login path across all nodes. In addition, the GUI interface for TotalView, when available, must be operational and accessible from the compute nodes of any allocated system.