Progress
Debugger Guide


Windows Initialization

You can specify Debugger initialization parameters in Windows using the Registry or the PROGRESS.INI file provided with your Progress installation. Note that if you plan to make changes to the defaults, make them to a copy stored in your working directory.

Search Order for PROGRESS.INI

When the Debugger starts up, it searches either in the Registry or for a PROGRESS.INI file. For information about the search order for the PROGRESS.INI file, see the chapter on maintaining user environments in the Progress Client Deployment Guide.

PROGRESS.INI Sections for Debugger Initialization

This file provides three sections for Debugger initialization, labeled with the following headings:

CAUTION: There are certain parameters in the PROGRESS.INI file that you must never change in a text editor. These are labeled Do Not Change in the following descriptions. You can set them reliably only from the Debugger using the Options Save Settings menu option. Any attempt to change these parameters outside of the Debugger can result in loss of data.
[Debug-Init] Section

This section includes several parameters that specify basic initialization options for the Debugger. They determine how the Debugger and its window start up in your environment, and include:

[Debug-Macros] Section

This section includes a list of parameters that define initial macros. The macros defined in this section take effect after any defined in the initial command file specified by the DebuggerInput parameter in the [Debug-Init] section. Specify these parameters in the following form:

SYNTAX
Macron = macro-name , command [ ; command ] ... 

Each macro parameter is identified by an integer (n) that must start at 0 and increment by 1 for each additional macro definition. The name of the macro (macro-name) can include any alphanumeric characters, and is case sensitive. Each command (command) can specify any Debugger command, except the BUTTON or MACRO commands, or a previously defined macro command. The maximum length of each macro definition to the right of the equal sign (=) is 255 characters.

In general, you can define an initial macro by using Debugger variables and following the same rules as any macro definition entered from the Debugger. For more information, see the MACRO command reference entry in "Command Reference," and the "Defining and Using Macros and Buttons" section in Running a Debugging Session."

NOTE: If you define and save macros during a debugging session, the Debugger stores the macro definitions in this section of your PROGRESS.INI file. For more information on saving macro definitions, see Debugger Window."

[Debug-Buttons] Section

This section includes a list of parameters that define initial buttons. The buttons defined in the [Debug-Buttons] section take effect after any buttons defined in the initial command file specified by the DebuggerInput parameter in the [Debug-Init] section. Specify these parameters in the following form:

SYNTAX
Buttonn = button-label , command [ ; command ] ... 

Each button parameter is identified by an integer (n) that must start at 0 and increment by 1 for each additional button definition. The label for the button (button-label) can include any alphanumeric characters, including embedded spaces, and is case sensitive. Unlike button labels defined using the BUTTON command, no quotes are allowed in these parameter definitions. Each command (command) can specify any Debugger command, except the BUTTON or MACRO commands, or a previously defined macro command. The maximum length of each button definition to the right of the equal sign (=) is 255 characters.

Except for quoting the button label (for example, to embed spaces), you can define an initial button by using Debugger variables and following the same rules as any button definition entered from the Debugger. For more information, see the BUTTON Command in "Command Reference," and the "Defining and Using Macros and Buttons" section in Running a Debugging Session."

NOTE: If you define and save buttons during a debugging session, the Debugger stores the button definitions in this section of your PROGRESS.INI file. For more information on saving button definitions, see Debugger Window."


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095