
UDI Developer’s Toolkit
Universal Debugger Interface Specification
6-3
HP/UX bundled C compiler
DOS IPC code, real–mode DFEs and TIPs
Microsoft C 7.0
DOS IPC code, protected–mode DFEs and TIPs
MetaWare High C
r
386 3.1 compiler plus Phar Lap 4.0 linker,
assembler, and DOS extender
Watcom 386 9.x compiler and linker plus Phar Lap 4.0 assembler and
DOS extender
NOTE:
The DOS IPC code for protected–mode DFEs and TIPs is dependent
on the Phar Lap DOS extender.
If you plan to use a different host development environment and you find that
modifications to the IPC source code are necessary to get it to build in that
environment, please send e–mail to udi@amd.com and any such changes can
be folded into the next version of the sources.
The sample IPC source code also has some limitations based on making some
simplifying assumptions about the DFE or TIP:
The UNIX socket IPC source code assumes that the host is big–endian. If
you want to use this code on a little–endian host, you will have to swap
the endian type of the appropriate fields when building the IPC messages.
See the discussion in Chapter 5 on the endianness of fields in socket IPC
messages.
Although the IPC methods allow multiple TIPs per DFE and multiple
DFEs per TIP, both the UNIX socket IPC source code and the DOS IPC
source code assume that a DFE connects to, at most, one TIP and that a
TIP gets connected to, at most, one DFE. On DOS IPC, the sender of a
message always includes the proper
connection_id
in the message but the
receiver of a message does not check the
connection_id
. On UNIX IPC,
messages are always sent on the correct socket but DFEs and TIPs only
listen on a single socket when listening for replies. Thus, DFEs and TIPs
built with the sample IPC code should interoperate properly with TIPs and
DFEs that do support multiple connections.