To Trace Activity Leading Up To A Program Halt; To Capture A Continuous Stream Of Program Execution No Matter How Large Your Program - HP 64782 User Manual

For the graphical user interface
Hide thumbs Also See for 64782:
Table of Contents

Advertisement

To trace activity leading up to a program halt

Choose Trace→Until Stop.
Using the command line, trace on a program halt by entering:
trace on_halt
The above commands cause the analyzer to continuously fill the trace buffer
until you issue a Trace→Stop or stop_trace command.
Sometimes you may have a program failure that can't be attributed to a
specific trigger condition. For example, the emulator may access guarded
memory and break to the monitor. You want to trace the events leading up to
the guarded memory access but you don't know what to specify for a trigger.
Use the above command. The analyzer will capture and record states until
the break occurs. The trace list will display the last processor states leading
up to the break condition.
Note that the trace until stop command may not capture the desired
information when you are using a foreground monitor (unless the code that
causes the break also causes the processor to halt) because the analyzer will
continue to capture foreground monitor states after the break. When using a
foreground monitor, you can use the command line to enter a trace command
that stores only states outside the range of the foreground monitor program
(for example, trace on_halt only not range <mon_start_addr> thru
<mon_end_addr> on_halt).
To capture a continuous stream of program execution
no matter how large your program
The following example can be performed in emulation systems using the
deep analyzer (it cannot be done with the 1K analyzer). It shows you how to
capture all of the execution of your target program. You may wish to capture
target program execution for storage, for future reference, and/or for
comparison with execution after making program modifications. The
execution of a typical target program will require more memory space than is
available in the trace memory of an analyzer. This example shows you how to
capture all of your target program execution while excluding unwanted
execution of the emulation monitor.
Using the Emulation Analyzer
To trace activity leading up to a program halt
219

Advertisement

Table of Contents
loading

Table of Contents