
UDI Developer’s Toolkit
B-2
Universal Debugger Interface Specification
For the DOS IPC, 1.2 TIPs did not support multiple connections.
They will ignore the
connection_id
field except on the
UDIDisconnect
call.
For the UNIX Socket IPC, in a response message from the 1.2 TIP,
the
response_code
field will not be present. Since the 1.2 TIP will not
make any
UDIDFE
xxx
requests, the DFE knows the first message that
comes back on the socket is the response.
For the UNIX Socket IPC, the
UDIFind
and
UDICapabilities_13
requests cannot be used.
For the UNIX Socket IPC, 1.2 TIPs do not support multiple
connections.
TIPs talking to 1.3 DFEs:
For the UNIX Socket IPC, all host–endian fields are sent big endian
(even when both the DFE and TIP are little endian).
Cannot pass a fine state in the
UDIWait
.
StopReason
when the gross
state is
UDIRunning
or
UDIHalted
. Cannot use negative fine states.
Only UDI error numbers through 41 can be returned.
TIPs talking to 1.2 DFEs have all the above 1.3 restrictions, plus:
Cannot use any of the
UDIDFE
xxx
calls.
Can return, at most, 80 characters in
TIPString
of
UDICapabilities
.
For the DOS IPC, only one 1.2 DFE connection should be allowed.
The
connection_id
parameter from a 1.2 DFE is not valid (except on
UDIDisconnect
) and must be ignored on other calls.
For the DOS IPC, the 1.2 DFE will call
UDIConnect_12
and the
UDICapabilities_12
table entries rather than their 1.3 and later
entries.
For the UNIX Socket IPC, the
response_code
field must be omitted in
all response messages back to the DFE. Since you cannot make any
UDI DFE
requests, the DFE knows the first message that comes back
on the socket is the response.