Oracle® Solaris Studio 12.4: dbxtool Tutorial

Exit Print View

Updated: October 2014

Step 6: More Breakpoint Counts

    To find out whether err_silent was wrong before or after the call to printField(), put a breakpoint in printField().

  1. Select printField(), right-click, and choose New Breakpoint.

    The New breakpoint type is pre-selected and the Function field is pre-populated with printfield.

  2. Click OK.

    image:New Breakpoint dialog box
  3. Click Restart image:Restart button .

    The first time you hit the breakpoint is during the first run, on the first stop, and on the first field, var.a. err_silent is 0, which is OK.

    image:Editor window with balloon evaluation
  4. Click Continue.

    err_silent is still OK.

  5. Click Continue again.

    err_silent is still OK.

Reaching the particular call to printField() that resulted in the unwanted error message might take a while. You need to use a breakpoint count on the printField breakpoint. But what shall the count be set to? In this simple example, you could attempt to count the runs and the stops and the fields being displayed, but in practice the process might be more difficult. There is a way to determine the count semi-automatically.