wdbgstrt.gml

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

.sy Two
option described below.

.note /Ega43
.ix 'display' 'changing lines'
.ix 'screen' 'number of lines'
.ix 'options' 'Ega43'
.ix 'Ega43 option'
.ix 'EGA lines'
When an Enhanced Graphics Adapter (EGA) is present, 43 lines of
output are displayed by a character mode debugger.

.note /Vga50
.ix 'display' 'changing lines'
.ix 'screen' 'number of lines'
.ix 'options' 'Vga50'
.ix 'Vga50 option'
.ix 'VGA lines'
When a Video Graphics Array (VGA) is present, 50 lines of output
are displayed by a character mode debugger.

.note /Overwrite
.ix 'options' 'Overwrite'
.ix 'Overwrite option'
specifies that the debugger's output can overwrite program output.
In this mode, the application and the debugger are forced to share the
same display area.
.np
.bi Do not use this option if you wish to debug a DOS graphics-mode application.

.note /Two
.ix 'options' 'Two'
.ix 'Two option'
specifies that a second monitor is connected to the system.
If the monitor type
.sy (Monochrome, Color, Colour, Ega43, Vga50)
is not specified then the monitor that is not currently being used is
selected for the debugger's screen.
If the monitor type is specified then the monitor corresponding to that
type is used for the debugger's screen.
.bi This option may be used when debugging a DOS graphics-mode application on
.bi the same machine and a second monitor is available.

.endnote
.*
.section *refid=dosopt DOS Specific Options
.*
.np
Use the following switches for the DOS debuggers. For more DOS options,
refer to the section called :HDREF refid='dwopt'..
.begnote $break

.note /Page
.ix 'options' 'Page'
.ix 'Page option'
specifies that page 0 of screen memory is to be used for the
application's screen and that page 1 of screen memory should be used
for the debugger's screen.
This option may be selected when using a graphics adapter such as the
CGA, EGA or VGA.
Using the
.sy Page
option results in faster switching between the application and debugger
screens and makes use of the extra screen memory available with the
adapter.  This is the default display option.
.bi Do not use this option if you wish to debug a DOS graphics-mode application.

.note /Swap
.ix 'options' 'Swap'
.ix 'Swap option'
specifies that the application's screen memory and the debugger's
screen memory are to be swapped back and forth using a single page.
The debugger allocates an area in its own data space for the inactive
screen.
This reduces the amount of memory available to the application.
It also takes more time to switch between the application and debugger
screens.
.bi This option MUST be used when debugging a DOS graphics-mode application
.bi and a second monitor is not available.

.np
The default display options are:
.autopoint
.point
If you have a two display system, the debugger uses both displays with
the program output appearing on the active monitor and the debugger
output appearing on the alternate monitor.
In other words, the
.sy Two
option is selected by default.
.point
If you have one of the CGA, EGA or VGA graphics adapters installed in
your system then the debugger selects the
.sy Page
option by default.
.point
Under all other circumstances, the debugger selects the
.sy Swap
option by default.
.endpoint

.note /CHecksize=number
.ix 'options' 'CHecksize'
.ix 'CHecksize option'
.ix 'SYSTEM'
specifies the minimum amount of storage, in kilobytes, that the
debugger is to provide to DOS for the purpose of spawning a program
while the debugger is active.
.bi This option is useful when the application that is being debugged uses
.bi up most or all of available storage, leaving insufficient memory to
.bi spawn secondary programs.
In order to provide the requested amount of free memory to DOS, the
debugger will checkpoint as much of the application as required.
.np
Checkpointing involves temporarily storing a portion of the
memory-resident application on disk and then reusing the part of
memory that it occupied for the spawned program. When the spawned
program terminates, the checkpointed part of the application is
restored to memory.
.np
The default amount is 0K bytes. In this case, the spawned program may
or may not be run depending on how much free storage is available to
DOS to run the program.
.begnote
.note Warning:
If the application being debugged installs one or more interrupt
handlers, the use of this option could hang your system. Your system
could lock up if the debugger checkpoints a portion of the
application's code that contains an interrupt handler.
.endnote

.note /NOCHarremap
.ix 'options' 'NOCHarremap'
.ix 'NOCHarremap option'
turns off the character re-mapping that the DOS debugger uses for
displaying dialogs and window frames.
.bi Use this option when trying to debug in
.bi an environment where character remapping is not available.
Windowed DOS boxes under OS/2 do not support character re-mapping.

.note /NOGraphicsmouse
.ix 'options' 'NOGraphicsmouse'
.ix 'NOGraphicsmouse option'
Turn off the graphics mouse emulation code that makes the mouse
cursor look like an arrow instead of a block.
.bi Use this option
.bi if the mouse cursor appears as 4 line drawing characters
.bi instead of an arrow.

.endnote
.*
.section *refid=winopt Windows Specific Options
.*
.np
Use the following switches for the Windows character-mode debugger.
Refer to the section called :HDREF refid='dwopt'. for more Windows
options.
.begnote $break

.note /Fastswap
.ix 'options' 'Fastswap'
.ix 'Fastswap option'
specifies that Windows 3.x screen memory and the debugger's screen
memory are to be swapped back and forth using a technique that is
faster than the default method of screen swapping but not
guaranteed to work for all video adapters.  This option applies to
Windows 3.x only.  By default, the Windows 3.x version of the
debugger uses a more conservative (and slower) method that works
with all video adapters.

.endnote
.*
.section *refid=linuxopt Linux Options
.*
.np
You can use the following switch for the Linux debugger.
.begnote $break

.note -Console=console_spec
.ix 'options' 'Console'
.ix 'Console option'
specifies the virtual console to use for debugger windows.
This may be a console number as in the following example.
.exam begin
-console=2
.exam end
.np
You may also use a full device name.
.exam begin
-console=/dev/tty
.exam end
.np
In this case, the debugger will use that device for its input and
output. The debugger/application screen flipping features will be
disabled.
.np
You can also optionally follow the device name with a colon and a
terminal type.
.exam begin
-con=/dev/tty:vt240
.exam end
.pc
This will let the debugger know what kind of terminal it's talking to
so it can initialize the user interface appropriately.

.note -COlumns=n
.ix 'options' 'COlumns'
.ix 'COlumns option'
specifies the number of columns of the screen/window that the debugger
should attempt to establish.

.note -XConfig=string
.ix 'options' 'XConfig'
.ix 'XConfig option'
specifies a set of X Windows configuration options to pass to
.bd xterm.
The following example sets the
.bd xterm
font size to 12 point.
.exam begin
-xc=-fs -xc=12
.exam end

.endnote
.*
.section *refid=qnxopt QNX Options
.*
.np
You can use the following switch for the QNX debugger.
.begnote $break

.note -Console=console_spec
.ix 'options' 'Console'
.ix 'Console option'
specifies the virtual console to use for debugger windows.
This may be a console number as in the following example.
.exam begin
-console=2
.exam end
.np
You may also use a full device name.
.exam begin
-console=//23/dev/ser1
.exam end
.np
In this case, the debugger will use that device for its input and
output. The debugger/application screen flipping features will be
disabled.
.np
You can also optionally follow the device name with a colon and a
terminal type.
.exam begin
-con=/dev/ttyp1:vt240
.exam end
.pc
This will let the debugger know what kind of terminal it's talking to
so it can initialize the user interface appropriately.

.note -COlumns=n
.ix 'options' 'COlumns'
.ix 'COlumns option'
specifies the number of columns of the screen/window that the debugger
should attempt to establish.

.note -XConfig=string
.ix 'options' 'XConfig'
.ix 'XConfig option'
specifies a set of X Windows configuration options to pass to
.bd xqsh.

.endnote
.*
.section *refid=videvar Environment Variables
.*
.np
You can use the
.ev &dbgvarup.
environment variable to specify default options to be used by the
debugger. Once you have defined the environment variable, those
options are used each time you start the debugger.
.*
.beglevel
.*
.section &dbgcmdup Environment Variable
.*
.np
If the specification of an option involves the use of an "="
character, use the "#" character in its place. This is required by
the syntax of the "SET" command.  Options found in the environment
variable are processed before options specified on the command line.
The following example illustrates how to define default options for the
debugger:
.ix 'environment variables' '&dbgcmdup'
.ix '&dbgcmdup environment variable'
.ix 'options' 'default'
.exam begin
C>set &dbgcmd=/swap/lines#50
.exam end
.*
.section &dbgcmdup Environment Variable in Linux
.*
.np
.ix 'environment variables' '&dbgcmdup'
.ix '&dbgcmdup environment variable'
.ix 'options' 'default'
The following example illustrates how to define default options for the
debugger under Linux:
.exam begin
$ export &dbgcmdup="-rows=50 -cols=100"
.exam end
.pc
Under Linux, care must be taken to specify the environment variable name
entirely in uppercase letters.
.np
.*
.section &dbgcmdup Environment Variable in QNX
.*
.np
.ix 'environment variables' '&dbgcmdup'
.ix '&dbgcmdup environment variable'
.ix 'options' 'default'
The following example illustrates how to define default options for the
debugger under QNX:
.exam begin
$ export "&dbgcmdup=-nofpu -console=3"
.exam end
.pc
Under QNX, care must be taken to specify the environment variable name
entirely in uppercase letters.
.np
.endlevel