TotalView Users Guide - CI Wiki

Defining Eval Points and Conditional Breakpoints
TotalView evaluates code fragments in the context of the target program.
This means that you can refer to program variables and branch to places in
your program.
If you call a function from in an eval point and there’s a breakpoint within that function,
TotalView will stop execution at that point. Similarly, if there’s an eval point in the
function, TotalView also evaluates that eval point.
For information on what you can include in code fragments, refer to “Using
Programming Language Elements” on page 385.
Eval points only modify the processes being debugged—they do not modify
your source program or create a permanent patch in the executable. If you
save a program’s action points, however, TotalView reapplies the eval point
whenever you start a debugging session for that program. For information
about how to save your eval points, see“Saving Action Points to a File” on
page 380.
You should stop a process before setting an eval point in it. This ensures that the eval
point is set in a stable context.
Setting Eval Points
This section contains the steps you must follow to create an eval point.
These steps are as follows:
1 Display the Action Point > Properties Dialog Box. You can do this, for
example, by right-clicking a icon and selecting Properties or by
selecting a line and then invoking the command from the menu bar.
2 Select the Evaluate button at the top of the dialog box.
3 Select the button (if it isn’t already selected) for the language in which you
plan to write the fragment.
4 Type the code fragment. For information on supported C, Fortran, and
assembler language constructs, see “Using Programming Language Elements”
on page 385.
5 For multi-process programs, decide whether to share the eval point
among all processes in the program’s share group. By default, TotalView
selects the Plant in share group check box for multi-process programs,
but you can override this by clearing this setting.
6 Select the OK button to confirm your changes.
If the code fragment has an error, TotalView displays an error message.
Otherwise, it processes the code, closes the dialog box, and places
an icon on the line number in the Source Pane.
CLI: dbreak –e
dbarrier –e
The variables that you refer to in your eval point can either have a global
scope or be local to the block of the line that contains the eval point. If you
declare a variable in the eval point, its scope is the block that contains the
TotalView Users Guide: version 8.7 367