wd
debugger command (WATCOM)
Syntax:
wd {-options} [:sym_file] [cmd_line]
Options:
- -TRap=trap_file[;trap_parm]
- the trap file to be used to control the application being debugged,
or to communicate across a remote link
If you use the ;trap_parm parameter, you'll likely need to put the option in quotes to avoid having the shell interpret the semi-colon.
- -LInes=n
- the number of lines used by the debugger
- -COlumns=n
- the number of columns used by the debugger
- -Invoke=file
- an alternate name for the debugger configuration file that's to be used at start-up time. The default file name is wd.dbg.
- -NOInvoke
- don't invoke the default debugger configuration file
- -NOMouse
- ignore any attached mouse.
- -Dynamic=number
- the amount of dynamic storage that the debugger is to set aside for its own use on startup. The default is 500K bytes. The larger the amount, the less memory is available for the application to be debugged.
- -REMotefiles
- look for all source files and debugger files on the remote machine.
- -NOFpu
- ignore the presence of a math coprocessor
- -NOSymbols
- omit all debugging information when loading an executable image.
- -DIP=dipname
- load a non-default Debug information processor (DIP). This option is generally not needed since the debugger loads all DIPs that it finds by default.
- -Console=number
- the virtual console number to use for debugger windows.
By default, the debugger uses the first unused virtual console.
You can also specify a full device name, and optionally follow the device name with a colon and a terminal type, such as
-console=//23/dev/ser1 -console=/dev/ttyp1:vt240
If you're in Photon, wd creates a new pterm window, and ignores the -Console option.
Description:
This command starts the Watcom Debugger. The cmd_line argument is one of the following:
- [//nid] pid
- [//nid] executable {arguments}
The optional nid argument identifies the node you want to run the program on. The two forms of cmd_line allow you to debug:
- a currently executing process by specifying its process ID as the pid argument
- an executable file by specifying its name and arguments as executable {arguments}
In both cases you can specify the node on which the process or executable is found.
The optional sym_file argument specifies the name of the file, usually with extension .sym, in which debugging information for the program is found.