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.

Setting Breakpoints and Barriers<br />

Figure 223: Setting<br />

Breakpoints on Multiple<br />

Similar Addresses<br />

� “Setting Machine-Level Breakpoints” on page 358<br />

� “Setting Breakpoints for Multiple Processes” on page 359<br />

� “Setting Breakpoints When Using the fork()/execve() Functions” on page 361<br />

� “Setting Barrier Points” on page 362<br />

Setting Source-Level Breakpoints<br />

Typically, you set and clear breakpoints before you start a process. To set a<br />

source-level breakpoint, select a boxed line number in the Process Window.<br />

(A boxed line number indicates that the line is associated with executable<br />

code.) A icon lets you know that a breakpoint is set immediately<br />

before the source statement.<br />

CLI: @ next to the line number<br />

You can also set a breakpoint while a process is running by selecting a<br />

boxed line number in the Process Window.<br />

CLI: Use dbreak whenever the CLI displays a prompt.<br />

Choosing Source Lines<br />

If you’re using C++ templates, <strong>TotalView</strong> sets a breakpoint in all instantiations<br />

of that template. If this isn’t what you want, clear the button and then<br />

select the Addresses button in the Action Point Properties Dialog Box. You<br />

can now clear locations where the action point shouldn’t be set. (See<br />

Figure 223.)<br />

352 Chapter 16: Setting Action Points

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

Saved successfully!

Ooh no, something went wrong!