
UDI Developer’s Toolkit
6-12
Universal Debugger Interface Specification
Notes for DOS Development
You can use the UDI Toolkit to develop both real–mode and protected–mode
DFEs and TIPs for PC hosts.
Real–Mode DFEs and TIPs
The targets,
dosdfe/smalldfe.exe
and
dostip/smalltip.exe
, under
src/uditools/makefile.pc
can be used as templates for real–mode DFE and TIP
development on PC hosts. Further examples are available in the
minimon
tree
in the
src/minimon/host/makepc.bat
file.
All the sources provided in this toolkit have been compiled on DOS using the
Microsoft C 7.0 compiler.
The memory model of the DFE is not critical since the IPC code will force far
calls with far pointer parameters to the TIP. The DFE stack is used for the
duration of a UDI call so you may want to increase the DFE stack size.
The memory model of the TIP must be large model. Also, because the TIP
procedures are basically called using the DFE’s stack pointer, the model flags
-
Alfu
(DS loaded on procedure entry; DS != SS) must be used.
The TIP’s stack should be as small as possible (it is not used once the TIP
becomes resident). Note also the use of the /CP:1 parameter in the link
command line for
montip
. This greatly reduces the footprint of the TIP.
When the DFE disconnects from the TIP with the
UDITerminateSession
parameter, you should find that the TIP has been removed from memory by the
IPC layer. If it has not been removed, either the DFE did not call disconnect or
the TIP returned an error on
UDIDisconnect
.
Protected–Mode DFEs and TIPs
The toolkit can also be used to build 386 protected–mode DFEs and TIPs.
Real–mode and protected–mode DFEs and TIPs all use the same real–mode
DOS IPC method and so all combinations can intercommunicate. In addition,
both the real–mode and the protected– mode DFEs and TIPs can work in a
DOS window initiated from within Microsoft Windows 3.0 or later.