
UDI Developer’s Toolkit
Universal Debugger Interface Specification
B-3
where:
tip_config_name
Is an arbitrary name which the DFE will use to refer to this
configuration. Each line in the UDI configuration file must have
a different
tip_config_name
field.
AF_UNIX
This address family should be used when the DFE and TIP are
running on the same host. This is the typical case.
AF_INET
This address family should be used when the DFE and TIP are
running on different hosts.
socket_name
Used only with AF_UNIX configurations. Specifies the socket
filename that will be used to communicate between the DFE and
TIP. The special socket name * indicates that a unique socket
filename should be generated automatically by the IPC layer.
This is useful if the user wants to have multiple DFEs connecting
to the same configuration name. If the
socket_name
is specified
explicitly, be aware that if any two AF_UNIX TIP configurations
are being used simultaneously, they must have unique
socket_names
. For DFEs that want to disconnect from a TIP and
then reconnect to that same TIP at some later time, an explicit
socket_name
is required.
tip_executable
Used only with AF_UNIX configurations. The DFE will use the
tip_executable
filename to spawn the TIP if the TIP is not already
running and listening at the indicated
socket_name
. If a full
pathname is not specified, the
PATH
environment variable is
used to locate the executable file. Note that when the
socket_name
is
*
, a new TIP executable is always created.
host_name
Used only with AF_INET
configurations. This specifies the name
of the host where the TIP is running.
port_number
Used only with AF_INET configurations. This specifies the
port_number
at which the TIP on the remote host is listening.
Note that in an AF_INET configuration, the TIP cannot be
created by the DFE and must already be running at the time of
the connection. The TIP on the remote host should be started with
a command line of: