FINDBP command
The FINDBP command provides full-screen search capability for line, statement and offset breakpoints in the source object. The FINDBP keyword cannot be abbreviated.
>>-FINDBP--+-------+--+----------+--;-------------------------->< +-FIRST-+ +-ENABLED--+ +-LAST--+ '-DISABLED-' +-NEXT--+ '-PREV--'
- FIRST
- Starts at the beginning of the source object and searches forward to find the first line, statement, or offset breakpoint.
- LAST
- Starts at the end of the source object and searches backward to find the last line, statement, or offset breakpoint.
- NEXT
- Starts at the next line after the current cursor location in the Source window and searches forward to find the next line, statement, or offset breakpoint
- PREV
- Starts at the previous line before the current cursor location in the Source window and searches backward to find the previous line, statement, or offset breakpoint
- ENABLED
- Restricts the searching to enabled breakpoints. The default is to list both enabled and disabled breakpoints.
- DISABLED
- Restricts the searching to disabled breakpoints. The default is to list both enabled and disabled breakpoints.
Usage notes
- If no operands are specified, a repeat FINDBP is
performed. A repeat FINDBP behaves in the following
ways:
- If the previous FINDBP command that you entered specified or implied the FIRST or NEXT parameter, Debug Tool uses the NEXT parameter.
- If the previous FINDBP command that you entered specified or implied the LAST or PREV parameter, Debug Tool uses the PREV parameter.
- If a repeat FINDBP immediately follows an unsuccessful FINDBP or repeat FINDBP, Debug Tool continues searching, wrapping from the last line to the first line. If the original direction of the FINDBP was backward to the beginning of the source object, Debug Tool wraps from the first line to the last line.
- If the previous FINDBP command that you entered specified or implied the ENABLED or DISABLED parameter, Debug Tool uses the ENABLED or DISABLED parameter, respectively.
- If you want to frequently use a repeat FINDBP, set a PF key (for example, PF17 or shift PF5) to FINDBP. For instructions on assigning a command to a PF key, see SET PFKEY command.
- Searches show the following behavior:
- If you specify FIRST, the search begins at the first line of the source object.
- If you specify LAST, the search begins at the last line of the source object.
- If you specify NEXT or the command defaults to NEXT and the cursor is on a source line or in its prefix or suffix area, the search begins at the line after the line the cursor is on.
- If you specify NEXT or the command defaults to NEXT and the cursor is not on a source line or in its prefix or suffix area, the search begins at the first line in the Source window.
- If you specify PREV or the command defaults to PREV and the cursor is on a source line or in its prefix or suffix area, the search begins at the line before the line the cursor is on.
- If you specify PREV or the command defaults to PREV and the cursor is not on a source line or in its prefix or suffix area, the search begins at the line before the first line in the Source window. If the first line of the source object is displayed, Debug Tool wraps to the end of the source object and continues with the last source line.
- If Debug Tool finds the breakpoint, Debug Tool scrolls the Source window so that you can see the breakpoint. Debug Tool places the cursor at the beginning of the prefix area for the source line that contains the breakpoint.
- If Debug Tool does not find the breakpoint, the screen does not change and the cursor is not moved. If you specified NEXT or PREV or the command defaults to NEXT or PREV and Debug Tool searched only part of the source object, then Debug Tool displays the message "Bottom of data reached" or "Top of data reached", as appropriate. If Debug Tool searched through the entire source object, then it displays the message "No line, statement or offset breakpoints were found".
- If multiple line or statement breakpoints exist on the same source line, the FINDBP command finds only one of them.
- The FINDBP command does not find AT STATEMENT * breakpoints.
- The FINDBP command searches only through the currently qualified compile unit, which is the compile unit visible in the Source window.
- Debug Tool does not log the FINDBP command.
- If you know the line number or statement number of the breakpoint you are looking for, the quickest way to find it is to use the SCROLL TO nnnnn or POSITION nnnnn command, which scrolls the Source window so that the line containing nnnnn in the prefix area is the first line in the Source window.
Examples
- Search for the next line in the Source window that contains
a line, statement, or offset breakpoint.
FINDBP
- Search for the first line in the source object that contains a
line, statement, or offset breakpoint. Then search for the next two
breakpoints.
FINDBP FIRST FINDBP FINDBP
Related references
- Related references
- AT LINE command
- AT OFFSET command (disassembly)
- AT STATEMENT command
- LIST AT command, with the LINE, OFFSET, or STATEMENT options
- POSITION command
- SCROLL command (full-screen mode), with the TO option
- SET PFKEY command