
October 13 1995, Draft 1
367
Chapter 7 Software Debugging
The Configuration File is found by first looking in the current working directory. If
not found, the file given by environment variable UDICONF is searched for. Lastly,
the executable PATH is searched. The format of these files is very similar, on UNIX:
session_id
session_id
AF_UNIX
AF_INET
socket_name
host_name
tip_exe tip_parameters
port
<not required>
The first column gives the session_id, which is used to select the appropriate
line. The
serial
key–word used with the “–TIP” option in the example, is compared
with the
session_id
for each line in the Configuration File. The first matching line
provides all the necessary data for connecting to a TIP process which is already run-
ning; or, if necessary, starting TIP process execution.
The second column gives the socket domain used by the socket IPC mechanism
connecting the two processes. Two domains are supported. The AF_UNIX domain
indicates both processes reside on the same host processor. Use of the AF_INET do-
main indicates the TIP process is on another networked host machine. In such a case,
the host name and socket port number are supplied in the following columns. The
UDI specification does not support DFEs starting TIP processes on remote hosts.
When the AF_INET domain is used to connect to the TIP, the TIP process must be
first up and running before connection is attempted.
When the AF_UNIX domain is used, the third column gives the name of the
socket used by the TIP to advertise its UDI services. If the DFE is unable to connect to
the named socket, it will assume the TIP is not running. In such a case the remaining
line information gives the name of the TIP executable and the start–up parameters.
Below is example
udi_soc
file contents.
mon
serial
iss
pcserver
cruncher
netrom
AF_UNIX
AF_UNIX
AF_UNIX
AF_UNIX
AF_INET
AF_UNIX
mon_soc
*
iss_soc
pc_soc
hotbox
net_soc
montip –t serial –baud 38400 –com /dev/ttya
montip –t serial –baud 9600 –com /dev/ttya
iss –r ../../src/osboot/sim/osboot
pcserver –t serial –baud 9600 –com /dev/ttya
7000
montip –t netrom –netaddr 163.181.22.41 ...
The relative path names given with
montip
start–up parameters, are relative to:
<montip executable directory>/../lib . The path given with the “–r” option is required
to find the OS–boot code for 29K start–up. When the DFE is always used to automati-
cally start the TIP process, a “*” can be used for the socket name field. This causes the
DFE to generate a random name for the socket file. This file will be removed when
the DFE and TIP discontinue execution at the end of the debug session.
The DOS Configuration File (
udiconfs.txt
) format is a little simpler. There are
only three entry fields, as shown by the example below: