
Universal Debugger Interface Specification
B-1
Appendix D
D
Compatibility of UDI 1.4, 1.3, and 1.2 DFEs and TIPs
At the IPC level, UDI 1.4 TIPs can recognize a UDI 1.2 or UDI 1.3 DFE
because the version part of the incoming parameter,
Connect.DFEIPCId
, will
indicate an earlier version of UDI. For the special case of UDI 1.2 DOS IPC,
UDI 1.2 DFEs actually called a different procedure in the call table and can be
recognized that way.
UDI 1.4 DFEs can recognize a UDI 1.2 or UDI 1.3 TIP because the version
part of the returned parameter,
Connect.TIPIPCId
, will indicate an earlier
version of UDI. For the special case of UDI 1.2 DOS IPC, UDI 1.2 DFEs
recognize a 1.2 TIP because of the absence of the
Signature_13
field in the
TIPVecRec
.
UDI 1.4 DFEs and TIPs can interoperate with UDI 1.2 and UDI 1.3 DFEs and
TIPs if the following precautions are taken:
DFEs talking to 1.3 TIPs:
Can only use offset 0 (Real PC1) in
UDI29KPC
space.
For the UNIX Socket IPC, all host–endian fields are sent big endian
(even when both the DFE and TIP are little endian).
UDISetBreakpoint_14, UDIQueryBreakpoint_14 and UDIConnect_14
calls cannot be used. If used at the procedural interface of the AMD
sample implementation, the IPC will attempt to map to the
corresponding _13 call, returning an error if unable to map.
DFEs talking to 1.2 TIPs have all the above 1.3 restrictions, plus:
Cannot use
UDIFind
(newly introduced at UDI 1.3).
Will get back, at most, 80 characters in
TIPString
of
UDICapabilities
.
For the DOS IPC, the DFE cannot use any of the functions below the
Signature_13
field. The DFE must use the
UDIConnect_12
and the
UDICapabilities_12
table entries rather than their 1.3 and later
entries.