Table of Contents
Advertisement
Trace R egisters
Trace registers specify under what conditions trace information is collected. For example,
define a trace register called trace 1 that causes the FICE system to begin collecting trace
information when your program begins executing statement #12 and to stop collecting trace
information at statement #13.
* DEFINE TRCHEG tracel » :cmaker#12 TO comaker#13
To emulate with this trace register, enter the GO command:
*GO TRACE traoel
Note that with a trace register, you must use the TRACE option of the GO command and not
the USING option of the GO command.
Event Registers
Event registers control the event machines directly. For example, define an event register
called qwriteinpay.
* DEFINE EVTREG qwriteinpay - 0 0
* *$EM SO IF READ AT ,:ernak*r.quarters IS 2 THEN GOTO SI
* *
* *XEMf SO IF xmaker.payment THEN GOTO S3
* *
**ENB
To emulate with this event register, enter the following GO command:
Debug Registers Calling Debug Procedures
One advantage to using debug registers is that you can store them in a file for use in later debug
sessions. Another advantage is the ability to automatically execute a debug procedure when the
specification in the debug register is satisfied. For example, the debug register qwriteinpay
executes the debug procedure query when the event specification is satisfied. This debug
procedure must return a TRUE or FALSE value. If the value is TRUE, a break occurs, and the
FICE system enters interrogation mode. If the value is FALSE, a break occurs, but the FICE
system restarts emulation and does not enter interrogation mode.
* DEFINE EVTREG qwriteinpay « DQ
* *SEfiS SO IF READ AT *:einaker.quarfers IS 2 THEN GOTO S1
* *
* *XEM SO IF :cmaker.payment THEN GOTO S3
* *
* * CALL query
**END
Introduction to Using the PICE™ System
Sf IFXUNK THEN BREAK ELSE GOTO SO
S3 ALWAYS GOTO S3
S1 IFXUNKTHEN BREAK ELSE GOTO SO
S3 ALWAYS GOTO S3
3-37
Advertisement
Table of Contents
