
UDI Services Overview
Universal Debugger Interface Specification
2-5
For some TIPs on some hosts (for example, a DOS machine with a simulator
for a TIP), all execution occurs when the DFE calls
UDIWait
. Consequently, a
DFE may not assume that any progress has been made by the sequence:
UDIExecute
, long delay,
UDIStop
(and a DFE must call
UDIWait
to ensure
progress). If the process is stopped,
UDIWait
returns the reason that the
process stopped.
Resource Access
The services in this group provide read and write access to target resources.
Services are available to move from host to target, to move from target to host,
to move from target to target, and to search target memory. A simple search of
target memory capability is also available.
The resource access functions are:
UDIRead
and
UDIWrite
Provide access to TIP resources
memory and registers.
1
, including
UDICopy
Produces target copies between resources.
This can be used to copy or fill memory by use
of the direction parameter.
UDIFind
Tells the TIP to report the occurrences of a
specified pattern in a given range of memory
or other resource. A pattern mask can be used
to further qualify the search.
Programmed I/O
Services in this group allow the user to communicate directly with a program
being debugged. Because the DFE ideally has complete control of the user
interface, while the TIP provides all target operating system services, the UDI
services in this group allow the DFE to manage the user interface for the
process.
1
Some TIPs may include additional resources, such as queues or semaphores associated with
an operating system, or special hardware features associated with an emulator. A DFE must
be TIP–aware to use these additional resources.