Table of Contents
Advertisement
Center
End
The trigger state will always be line number 0 in the trace list.
Interaction with trace commands
The Trace Trigger, Breakpt Access, Breakpt Read, and Breakpt Write
commands all require use of emulation analyzer resources. If access
breakpoints are active (indicated by the message TRC: BrkRWA on the status
line), then a Trace Trigger command may not be entered. If a trace trigger is
active, access breakpoints may not be entered.
The Breakpt commands set up a trace with the trigger at the end of the trace
buffer, using the current storage qualification. You can display the trace after
the break occurs to see the cycles leading up to the break.
See Also
Breakpt Access
Breakpt Read
Breakpt Write
Trace Trigger Event
Trace Trigger List
Trace Trigger None
Debugger Option Trace Fetch_Align
Examples
To trigger the trace measurement on entry into function
update_state_of_system and position the trigger state in the center of
the trace memory buffer:
Trace Trigger Address Is update_state_of_system Status
Is FnCde Prog PosnTrig Center
To trigger the trace measurement on the occurrence of a write to variable
time_struct.seconds, and halt (break) program execution on detection of the
trigger condition:
Trace Event Specify 6 <Tab> Address Is
&time_struct.seconds <Tab> Data Is 0x3c Status Is Write
<Tab> BrkOnTrg
The trigger is centered in the trace buffer.
The trigger is at the end of the trace buffer.
Chapter 12:
Trace Trigger
503
Advertisement
Table of Contents
