wdbgrem.gml

开放源码的编译器open watcom 1.6.0版的源代码

.section *refid=remnov NOV (Novell SPX)
.*
.ix 'Novell SPX remote debugging'
.ix 'remote debugging' 'Novell SPX'
.np
This link communicates over a Novell Network. In order to use this
link, you must have a NetWare requester installed on both machines. Be
sure that it is configured to include the SPX option. Consult your
NetWare documentation for details.
.np
The parameter to this link is an arbitrary name to be used for the
connection. This allows multiple network users users to remote debug
simultaneously. The default name is NovLink. If the remote server will
not start, try specifying a different name for the link. The following
example shows how to use the default link parameters:
.millust begin
A>novserv
B>&dbgcmd. /tr=nov app
.millust end
.np
The following example shows how to name "john" as a link parameter:
.millust begin
A>novserv john
B>&dbgcmd. /tr=nov;john app
.millust end
.*
.section *refid=remnet NET (NetBIOS)
.*
.np
This link communicates over NetBIOS. In order to use this link, you
must have NetBIOS installed on both machines. Consult your network
documentation for details.
.np
The parameter to this link is an arbitrary name to be used for the
connection. This allows multiple network users users to remote debug
simultaneously. The default name is NetLink. The following example
shows how to use the default link parameters.
.millust begin
A>netserv
B>&dbgcmd. /tr=net app
.millust end
.np
The following example shows how to use the name "tammy" as a link
parameter.
.millust begin
A>netserv tammy
B>&dbgcmd. /tr=net;tammy app
.millust end
.*
.section *refid=rempar PAR (Parallel)
.*
.ix 'remote debugging' 'over parallel port'
.ix 'parallel port remote debugging'
.np
This link communicates over the parallel port. Three different cable
types may be used. They are called the LapLink, Flying Dutchman, and
Watcom cables. Although the Watcom cable will communicate considerably
faster than the other two, we have found it to be unreliable on some
printer cards.
.refalso vidwire
.np
The parameter to this link is a number from 1 to 3 or the letter "p"
followed by a hexadecimal printer I/O port address. This tells the
software which parallel port the cable is connected to (LPT1, LPT2,
LPT3). The default is 1. The parameter used on each side of the link
depends on which printer port the cable is plugged into on that
machine. It need not be the same on both sides. The following example
shows how to debug across a parallel cable plugged into printer port 3
on one machine and port 2 on the other.
.millust begin
A>parserv 3
B>&dbgcmd. /tr=par;2 app
.millust end
.np
As an alternative, you can specify a port address to use. It is less
convenient than specifying a port number but will work on systems like
OS/2 where the actual I/O port address cannot be obtained from the
system. The following example shows how to debug across a parallel
cable plugged into I/O port 0x378 on one machine and port 2 on the
other.
.millust begin
A>parserv p378
B>&dbgcmd. /tr=par;2 app
.millust end
.np
.ix dbgport.sys
.ix dbginst.exe
Windows NT Note: Under Windows NT/2000/XP you must have the dbgport.sys
device driver installed and loaded on your machine before the host
debugger will be able to access the parallel port. To install this file
manually, first copy it from %WATCOM%\binnt\dbgport.sys to
%WINDOWS%\system32\drivers. Once the file has been copied, run the
%WATCOM%\binnt\dbginst.exe program to install the device driver and
activate it. You will need to have system administrator permissions in
order to be able to run the dbginst.exe program. Once these two steps are
done, the parallel port debugger can work. Note also that if you
wish to do parallel port debuging on a target machine running Windows
NT/2000/XP, you will need to follow the same set of steps on the target
machine as well.
.np
If you are going to debug a DOS extender application, then you must
also specify a trap file to the server program. The trap file must be
specified before the port number. The following example shows how to
debug a 32-bit DOS/4GW application across a parallel cable plugged
into printer port 2 on one machine and port 3 on the other.
.millust begin
A>parserv /tr=rsi 2
B>&dbgcmd. /tr=par;3 app
.millust end
.np
The "RSI" trap file is specified for DOS/4G(W) applications.
You can specify other trap files for the other DOS extenders
(e.g., "CW" for CauseWay).
Do not forget to include other required files in the path.
.begnote
.*
.note CW
Both "CWSTUB.EXE" and the loader help file "CWHELP.EXE" must also be
located in one of the directories listed in the DOS
.ev PATH
environment variable.
See the section entitled :HDREF refid='vidcw'. for more information
on debugging applications that use the CauseWay DOS extender.
.*
.note RSI
Both "DOS4GW.EXE" and the loader help file "RSIHELP.EXP" must also be
located in one of the directories listed in the DOS
.ev PATH
environment variable.
See the section entitled :HDREF refid='vidrsi'. for more information
on debugging applications that use the DOS/4GW DOS extender.
.*
.note PLS
One or more of "RUN386.EXE" (or "TNT.EXE"), "DBGLIB.REX",
"PLSHELP.EXP", and "PEDHELP.EXP" must be located in one of the
directories listed in the DOS
.ev PATH
environment variable.
See the section entitled :HDREF refid='vidpls'. for more information
on debugging applications that use the Phar Lap DOS extender.
.*
.endnote
.*
.section *refid=remser SER (Serial)
.*
.ix 'remote debugging' 'over serial port'
.ix 'serial port remote debugging'
.np
This link communicates over the serial port. See the appendix entitled
:HDREF refid='vidwire'. for wiring details. The debugger and server
will automatically synchronize on a communications speed. They may
communicate at rates as high as 115kB. The DOS and OS/2 "mode" command
or the QNX "stty" commands need not be used.
.np
The parameter to this link takes the form
.millust begin
port_number.baud_rate
.millust end
.np
.mono port_number
is a number from 1 to 3 indicating which serial port the cable is
connected to. The default is 1.
.np
.mono baud_rate
is the maximum BAUD rate at which to communicate.
If you already know the maximum BAUD rate at which the two
machines will communicate, this parameter will speed up
the connection time by eliminating some of the synchronization protocol.
.np
.mono baud_rate
may be any of 115200, 57600, 38400, 19200, 9600, 4800, 2400, or 1200.
It may be shortened to the first 2 digits.
.np
A special BAUD rate of 0 is also allowed. This should be used
if the serial port has been pre-assigned using the "mode" or "stty"
commands. The pre-assigned BAUD rate is used and the BAUD rate
negotiation is avoided.  This will allow you to debug over a modem.
.np
The following example shows how to debug across a serial cable
using default settings:
.millust begin
A>serserv
B>&dbgcmd. /tr=ser app
.millust end
.np
The following example shows how to debug across a serial cable
using serial port 2 on each machine setting the maximum BAUD
rate to 9600:
.millust begin
A>serserv 2.9600
B>&dbgcmd. /tr=ser;2.9600 app
.millust end
.begnote
.note QNX 4 Note:
Under QNX 4, a node id may be specified followed by a comma if the
serial port is not located on the current node.
The command "serserv 3,1.9600" would use the device //3/dev/ser1 at a
BAUD rate of 9600.
Alternatively, you can specify a device such as /dev/foobar.
To specify the maximum line speed, you can specify something like
/dev/foobar.56.
Of course, you can also include a node id such as //5/dev/foobar.
.millust begin
A>serserv //3/dev/ser2.9600
B>&dbgcmd. /tr=ser;//5/dev/ser2.9600 app
.millust end
.endnote
.np
If you are going to debug a DOS extender application, then you must
also specify a trap file to the server program. The trap file must be
specified before the port number and BAUD rate. The following example
shows how to debug a 32-bit DOS/4GW application across a serial cable
using serial port 1 on one machine and serial port 2 on the other
machine setting the maximum BAUD rate to 9600 for each:
.millust begin
A>serserv /tr=rsi 1.9600
B>&dbgcmd. /tr=ser;2.9600 app
.millust end
.np
The "RSI" trap file is specified for DOS/4G(W) applications.
You can specify other trap files for the other DOS extenders
(e.g., "CW" for CauseWay).
Do not forget to include other required files in the path.
.begnote
.*
.note CW
Both "CWSTUB.EXE" and the loader help file "CWHELP.EXE" must also be
located in one of the directories listed in the DOS
.ev PATH
environment variable.
See the section entitled :HDREF refid='vidcw'. for more information
on debugging applications that use the CauseWay DOS extender.
.*
.note RSI
Both "DOS4GW.EXE" and the loader help file "RSIHELP.EXP" must also be
located in one of the directories listed in the DOS
.ev PATH
environment variable.
See the section entitled :HDREF refid='vidrsi'. for more information
on debugging applications that use the DOS/4GW DOS extender.
.*
.note PLS
One or more of "RUN386.EXE" (or "TNT.EXE"), "DBGLIB.REX",
"PLSHELP.EXP", and "PEDHELP.EXP" must be located in one of the
directories listed in the DOS
.ev PATH
environment variable.
See the section entitled :HDREF refid='vidpls'. for more information
on debugging applications that use the Phar Lap DOS extender.
.*
.endnote
.*
.section *refid=remwin WIN (Windows 3.x/9x Virtual DOS Machine)
.*
.np
.ix 'Windows' 'remote debugging'
.ix 'remote debugging' 'with Windows'
.ix 'Windows' 'enhanced mode'
This link communicates between 2 Windows DOS boxes. In order to use
this link, you must have Windows 3.x or Windows 95 installed on your
machine. You must run Windows 3.x in enhanced mode. You must also
include the "device" specification listed below in the [386Enh]
section of your "SYSTEM.INI" file (this line is usually added during
the &company software installation process).
.millust begin
DEVICE=C:&pathnamup.\BINW\WDEBUG.386
.millust end
.np
In order for this link to work properly, you must ensure that this
link runs in a DOS box that has background execution enabled.
.np
The parameter to this link is an arbitrary name to be used
for the connection. This allows you to have multiple remote
debug sessions active simultaneously. The default name is WinLink.
The following examples show how to use the default name or specify a
link name using the Windows 3.x/95 VDM link.
.millust begin
A>winserv
B>&dbgcmd. /tr=win app

A>winserv whats_in_a_name
B>&dbgcmd. /tr=win;whats_in_a_name app
.millust end
.np
The following examples show how to debug a 32-bit extended DOS
application using the Windows 3.x/95 VDM link.
.millust begin
A>winserv /tr=rsi
B>&dbgcmd. /tr=win app

A>winserv /tr=rsi whats_in_a_name
B>&dbgcmd. /tr=win;whats_in_a_name app
.millust end
.np
The "RSI" trap file is specified for DOS/4G(W) applications.
You can specify other trap files for the other DOS extenders
(e.g., "CW" for CauseWay).
Do not forget to include other required files in the path.
.begnote
.*
.note CW
Both "CWSTUB.EXE" and the loader help file "CWHELP.EXE" must also be
located in one of the directories listed in the DOS
.ev PATH
environment variable.
See the section entitled :HDREF refid='vidcw'. for more information
on debugging applications that use the CauseWay DOS extender.
.*
.note RSI
Both "DOS4GW.EXE" and the loader help file "RSIHELP.EXP" must also be
located in one of the directories listed in the DOS
.ev PATH
environment variable.
See the section entitled :HDREF refid='vidrsi'. for more information on
debugging applications that use the DOS/4GW DOS extender.
.*