Difference between revisions of "DISPLAY BREAKPOINT"
Yvonnemilne (Talk | contribs) |
Yvonnemilne (Talk | contribs) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Purpose== | ==Purpose== | ||
| − | + | Display active breakpoints when a program is being run in debug mode | |
| Line 18: | Line 12: | ||
==Description== | ==Description== | ||
| + | The DISPLAY BREAKPOINT command displays active breakpoints when a program is being run in debug mode. Breakpoints are logical conditions. A program executing in debug mode will stop and redisplay the debug popup when the breakpoint condition evaluates to true. | ||
| − | DISPLAY commands differ from LIST commands in that they pause every | + | DISPLAY commands differ from LIST commands in that they pause every screen until a key is pressed. You can cancel any further output at this point by pressing the [ABANDON] key. Where the output is sent to a file or printer, the pause is disabled. |
| Line 30: | Line 25: | ||
|- | |- | ||
|} | |} | ||
| + | |||
==Example== | ==Example== | ||
<code lang="recital"> | <code lang="recital"> | ||
| + | debug myapp | ||
| + | suspend | ||
display breakpoint | display breakpoint | ||
| + | resume | ||
</code> | </code> | ||
| + | |||
==Products== | ==Products== | ||
| + | Recital | ||
[[Category:Documentation]] | [[Category:Documentation]] | ||
[[Category:Commands]] | [[Category:Commands]] | ||
| + | [[Category:Error Handling and Debugging]] | ||
| + | [[Category:Error Handling and Debugging Commands]] | ||
Latest revision as of 11:46, 1 December 2009
Purpose
Display active breakpoints when a program is being run in debug mode
Syntax
DISPLAY BREAKPOINT [TO FILE <.txt filename> | (<expC>)] | [TO PRINT]
See Also
CANCEL, DEBUG, DISPLAY MEMORY, DISPLAY STATUS, DISPLAY WATCHPOINT, DO, LIST BREAKPOINT, LIST WATCHPOINT, QUIT, RESUME, SET COMPILE, SET DEVELOPMENT, SET STEP, SUSPEND
Description
The DISPLAY BREAKPOINT command displays active breakpoints when a program is being run in debug mode. Breakpoints are logical conditions. A program executing in debug mode will stop and redisplay the debug popup when the breakpoint condition evaluates to true.
DISPLAY commands differ from LIST commands in that they pause every screen until a key is pressed. You can cancel any further output at this point by pressing the [ABANDON] key. Where the output is sent to a file or printer, the pause is disabled.
| Keyword | Description |
|---|---|
| TO <file> | The display output will be sent to the specified file. The filename can be substituted with a <expC>, enclosed in round brackets, which returns a valid filename. If no file extension is specified, then ".txt" will be used. The command SET PAGELENGTH governs the output file pagination and SET PAGEWIDTH defines the width of each page. Page numbers are centered on the bottom of the page according to width. |
| TO PRINT | The display output will be sent to a printer. The TO PRINT option will default to a local printer unless the command SET PRINTER TO \\SPOOLER is issued. The print request will then be spooled to the system printer, which is defined by the environment variable DB_PRINT. |
Example
debug myapp suspend display breakpoint resume
Products
Recital
