30.01.2013 Views

TotalView Users Guide - CI Wiki

TotalView Users Guide - CI Wiki

TotalView Users Guide - CI Wiki

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

c<br />

h<br />

a<br />

p<br />

t<br />

e<br />

r<br />

16<br />

Setting<br />

Action Points<br />

This chapter explains how to use action points. <strong>TotalView</strong> has four<br />

kinds of action points:<br />

� A breakpoint stops execution of processes and threads that reach it.<br />

� A barrier point synchronizes a set of threads or processes at a location.<br />

� An eval point causes a code fragment to execute when it is reached.<br />

� A watchpoint lets you monitor a location in memory and stop execution<br />

when it changes.<br />

This chapter contains the following sections:<br />

� “About Action Points” on page 349<br />

� “Setting Breakpoints and Barriers” on page 351<br />

� “Defining Eval Points and Conditional Breakpoints” on page 366<br />

� “Using Watchpoints” on page 373<br />

� “Saving Action Points to a File” on page 380<br />

About Action Points<br />

Actions points lets you specify an action for <strong>TotalView</strong> to perform when a<br />

thread or process reaches a source line or machine instruction in your program.The<br />

different kinds of action points that you can use are shown in<br />

Figure 221 on page 350.<br />

� Breakpoints<br />

When a thread encounters a breakpoint, it stops at the breakpoint. Other<br />

threads in the process also stop. You can indicate that you want other<br />

related processes to stop, as well. Breakpoints are the simplest kind of<br />

action point.<br />

<strong>TotalView</strong> <strong>Users</strong> <strong>Guide</strong>:version 8.7 349

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!