About MSCF

HPC Center Mol Science Software Scientific Consulting Graphics & Vis Lab Partners & Links Research Highlights

Getting Started

Submitting Proposals Accounts Required 1st Time Logging In FAQ

Accounts

Getting An Account Managing Allocations User Support User Policies

Using Resources

File Systems MSCF Software Submit & Manage Jobs Store & Backup Data FAQ

Computer Hardware

Parallel Computers NWfs Graphics & Vis Workstations & Other

Software

Applications NWChem Ecce ParSoft Job Management Compilers System Software

Visualization

VisLab Virtual Tour Services Visualization Gallery Contacts Equipment List

Training

Software Tutorials Workshops/Classes Scientific Consulting User Docs for Apps

Events

Workshops/Classes Meetings

System Reports

System Announcements Current Job Sample NWfs Status User Tips

Click on the | above to Expand/Collapse the menu

•  Home 
•  Site Map 
•  Help 
•  Search 
•  Contacts 
•  Tips 
•  Glossary 
•  Tour 
•  Brochures 

Molecular Science Computing Facility
Computer Hardware

TotalView 6.3

What is TotalView

Etnus TotalView version 6.3 is a parallel and multithreaded application debugger that allows you to analyze your program flow, find bugs, and test and monitor program variables, all using an easy to use graphical user interface. The debugger supports the programming languages C, C++, Fortan 77/90/95, UPC, and supports the parallel programming models MPI, OpenMP, Pthreads and PVM.

Manual

The TotalView user guide, and other documentation, is available online. In addition, the consulting group has some copies of the TotalView Quickview reference guide are available upon request.

Preparing for your debugging session

Your code has to be compiled without optimization (i.e. -O0) and with the debug option (-g) set. Any optimization results in variables and data blocks being removed or changed by the compilers and this will confuse the debugger.

Starting your TotalView debugging session

Follow the procedure below to start a parallel TotalView debugging session:

• Get your interactive processors for the debug session:

  % bsub -n <# proc> -W <0:30> -P <account> -Is csh

• Start the parallel debugger on the processors:

  % /home/scicons/apps/totalview.6X.3.0-4/toolworks/totalview.6X.3.0-4/bin/totalview prun -a -n <number of processors> <your_program.x> <any input needed>

Once the debugger starts...

Once the debugger starts the user will see activity on the screen and the debugger will display the message that prun is halted. Continue by clicking run/continue. Now the debugger should be halting at the beginning of the user's code. The user will have two windows, a small overview window and a large window containing, among lots of other things, source code.
The debugger allows the user to control which processes to run, the user can set breakpoints that trigger all processes to stop when one process reaches this point, or only that particular process, etc.

For additional information about the debugger options the user is referred to the manuals. If you need additional help, please contact the MSCF-consulting group through the web mscf-consulting form or send email to mscf-consulting@emsl.pnl.gov.