GHS Config Option Descriptions

Save window positions and sizes

Permitted settings for this option are:

Selected (rememberWindowPositions on) — [default] Remembers the position and size of windows created by MULTI so that the next time a window of the same type is created, it appears in the same location and with the same size. For example, if you resize the Project Manager window, move it to a specific location on your screen, and then close the window, the next Project Manager you open appears in the same place and with the same size. The first window of a given type is positioned in the saved location. Any new windows of the same type are slightly offset from the location of the open window and are given the saved size. Size and position are remembered even after you exit and restart MULTI.
Cleared (rememberWindowPositions off) — Does not remember the position and size of windows created by MULTI.

Note: This setting does not apply to certain types of dialog boxes, such as modal dialog boxes, or to certain windows, such as the History window, the Active Licenses window, the Memory Test Wizard, the Perform Memory Test window, and the Source Path window. This setting does apply to the Data Explorer, but only the Data Explorer position is remembered. The Data Explorer window is automatically sized based on the data displayed within it and based on the configuration options Minimum initial size (WxH) and Maximum initial size (WxH), documented in "The Debugger Options Tab" in the MULTI: Building Applications book for your target.

Display close (x) buttons

Permitted settings for this option are:

Selected (closeButtonOnTitlebar on) — A Close button will appear on window toolbars. This option only affects new windows created after you change this setting, except for Debugger windows, which adjust to the new setting immediately.
Cleared (closeButtonOnTitlebar off) — [default] The Close button will not appear on toolbars.

Allow beeping

Permitted settings for this option are:

Selected (beep on) — [default] MULTI beeps on various error conditions, such as a search that does not match anything.
Cleared (beep off) — MULTI never beeps.

For information about the Beep Editor command, see "Miscellaneous Commands" in the MULTI: Building Applications book for your target.

Show tooltips

Linux/Solaris only

Permitted settings for this option are:

Selected (tooltips on) — [default] Tooltips (small explanatory boxes that pop up when you hover the cursor over a GUI item) will appear if available.
Cleared (tooltips off) — Tooltips will never appear.

In History, this setting only applies to toolbar buttons; other GUI items where tooltips may appear are not affected.

Match exact case in searches

Determines the case sensitivity of interactive text searches in the Editor and of incremental text searches in MULTI tools. Permitted settings for this option are:

Selected (exactCase on) — Searches are case-sensitive.
Cleared (exactCase off) — [default] Searches are case-insensitive.

This option can also be set on a per-Editor-window basis with the Search dialog box. For more information, see "Interactive Searching Using the Search Dialog Box" in the MULTI: Building Applications book for your target.

Note: This setting does not apply to the grep Editor or Debugger commands or to any of the Search in Files dialog boxes, all of which run grep and are case-sensitive by default.

Escape restores view after iSearch

Permitted settings for this option are:

Selected (iSearchReturn on) — Returns the cursor to its original position when you press Esc while in incremental search mode. See "Incremental Searching" in the MULTI: Building Applications book for your target.
Cleared (iSearchReturn off) — [default] Does not return the cursor to its original position when you press Esc while in incremental search mode.

Phase of moon in scroll bar box

We at Green Hills decry the unfortunate tendency in our society whereby mankind perceives itself as disconnected from its environment. We as individuals pay no attention to flowers blooming or leaves falling. We live immersed in our air conditioned offices and, if we are programmers, we never see the light of day. In a perhaps futile effort to stop this trend, we provide all MULTI users with the current phase of the moon to encourage them to leave their desks and look up at the beautiful night sky.

Permitted settings for this option are:

Selected (moon on) — Displays the approximate phase of the moon in the nook of the vertical and horizontal scroll bars.
Cleared (moon off) — [default] The phase of the moon is not displayed.

Changes to this setting only affect new windows.

Launch clipboard manager

Linux/Solaris only

Permitted settings for this option are:

Selected (clipManLaunch on) — [default] Runs the clipboard manager, which stores selections that have been sent to the clipboard by all applications. The contents of the clipboard are accessible after MULTI has exited.
Cleared (clipManLaunch off) — The contents of the clipboard are lost when MULTI exits.

Warp pointer

Permitted settings for this option are:

Never (warpPointer never) — [default for Windows] Never move the mouse pointer automatically. The mouse cursor can only be changed by physically moving the mouse.
Into Dialog Box (warpPointer intoDialogue) — [default for Linux/Solaris] Warp the mouse pointer to the default button of new dialog boxes that appear.
In & Out of Dialog Box (warpPointer in&OutDialogue) — Warp the mouse pointer into the default button of new dialog boxes, and warp it back to its previous location when the dialog box is closed.

Print command

Linux/Solaris only

(printCommand command) Specifies the command used by the Print Setup dialog box to send information to a printer (see "The Print Setup Dialog Box" in the MULTI: Building Applications book for your target). When you open the Print Setup dialog box, the specified command is displayed in the Print Command field if you have not previously printed anything by using a different command. Otherwise, the specified command is available from the Print Command drop-down list.

The default is lpr.

Editor

Specifies which editor MULTI uses when you request an editor to start. Permitted settings for this option are:

MULTI Editor (extEditor_Choice "multi editor") — [default] Uses the MULTI Editor.
Emacs (extEditor_Choice emacs) — Uses the Emacs Editor.
Vi (extEditor_Choice vi) — Uses the vi Editor.
Other (extEditor_Choice other) — Uses an editor that is not available in the list.

Version Control

Specifies which version control system MULTI uses. Permitted settings for this option are:

Auto Detect (versionControlType autoDetect) — [default] Version control is auto-detected based on the file currently in use.
Disable (versionControlType disable) — Version control is disabled.
CVS (Concurrent Versions System) (versionControlType cvs) — An open-sourcenetwork-transport version control system. See "Integrating with CVS" in the MULTI: Building Applications book for your target.
Subversion (versionControlType subversion) — An open-sourcenetwork-transport version control system. See "Integrating with Subversion" in the MULTI: Building Applications book for your target.
ClearCase (versionControlType clearCase) — A version control system from Rational Software. See "Integrating with ClearCase" in the MULTI: Building Applications book for your target.
SourceSafe (versionControlType sourceSafe) — (deprecated, Windows only) A version control system from Microsoft. See "Integrating with SourceSafe" in the MULTI: Building Applications book for your target.

Source Code Font

(font font_name) Opens a font selection dialog box in which you can set the source code font. This font is used for most textual display, including in the Debugger source pane, the command pane, History, and the MULTI Editor. Click Source Code Font and select a font installed on your system. The font you choose should normally be a fixed-width font so that characters align properly. Italic and oblique fonts should not be chosen. While some italic and oblique fonts work correctly, others exhibit drawing problems.

The default font on Windows is Consolas. The command to restore the default Windows font from the command pane is:

configure font "consolas:13"

(13 is the font height, not the point size.)

The default font on Linux/Solaris is misc fixed medium semi-condensed. The command to restore the default Linux/Solaris font from the command pane is:

configure font -misc-fixed-medium-r-semicondensed-*-*-120-*-*-*-*-*-*

With the following exception, all MULTI tools opened during the current MULTI session are notified of changes to this option. For more information, see "Propagating Configuration Settings" in the MULTI: Building Applications book for your target.

This option affects the font in History whether you are running Windows or Linux/Solaris. On Windows, changes to this option do not take effect until the next time History is launched.

GUI Font

(guiFont font_name) Opens a font selection dialog box in which you can set the GUI font. This font is used for buttons, menus, and other GUI controls. Click GUI Font and select a font installed on your system. Italic and oblique fonts should not be chosen. While some italic and oblique fonts work correctly, others exhibit drawing problems.

The default font on Windows is Tahoma Regular. The command to restore the default Windows font from the command pane is:

configure guiFont "tahoma:11"

The default font on Linux/Solaris is adobe helvetica medium. The command to restore the default Linux/Solaris font from the command pane is:

configure guiFont *-helvetica-medium-r-normal-*-12-*-*-*-*-*-*-*

All MULTI tools opened during the current MULTI session are notified of changes to this option. For more information, see "Propagating Configuration Settings" in the MULTI: Building Applications book for your target.

Use XTerm

Linux/Solaris only

(extEditor_EmacsUseXTerm for Emacs, extEditor_ViUseXTerm for vi, extEditor_OtherUseXTerm for other editors) Determines whether the external editor will be launched from within an xterm. This is equivalent to prefixing xterm -e to the command to launch the editor. Users with console mode editors should enable this option. You must restart MULTI for changes to this option to take effect.

Command line arguments

("extEditor_EmacsArgumentFormat +%LINE %FILE0 %FILES" for Emacs, "extEditor_ViArgumentFormat +%LINE %FILE0 %FILES" for vi, "extEditor_OtherArgumentFormat command line specification” for other editors) Determines the arguments given to the editor when it is launched.

Three special character sequences are replaced when the editor is run. Substitution rules follow:

%LINE — Replaced with the line number to go to when opening the file (removed if MULTI does not specify a line number).
%FILE0 — Replaced with the first file to be edited.
%FILES — Replaced with all but the first file if there is more than one file to edit (removed if MULTI only specifies one file to edit). Each file is separated by a space.

Mode

Permitted settings for this option are:

Disabled (taskbarType disabled) — Disables the Taskbar Organizer. In this mode, MULTI windows populate both the taskbar and the window list that appears when you press the AltTab key combination.
Taskbar (taskbarType taskbar) — Enables taskbar mode. In taskbar mode, all MULTI windows are grouped into a single taskbar entry labeled MULTI. For more information, see "Configuring Taskbar Organization" in the MULTI: Building Applications book for your target.
Tray (taskbarType tray) — Enables tray icon mode. In tray icon mode, all MULTI windows are grouped under a single system tray icon. For more information, see "Configuring Taskbar Organization" in the MULTI: Building Applications book for your target.

When pressing Alt-Tab, display

Allows you to configure the appearance of items in the AltTab list. Permitted settings for this option are:

All windows (taskbarShowAllWindows on) — Displays all MULTI windows in the AltTab list.
Only the Taskbar Organizer (taskbarShowAllWindows off) — Displays a single MULTI icon in the AltTab list, regardless of the number of open MULTI windows. The setting of the option When selecting the organizer in the Alt-Tab list determines the behavior of the MULTI icon when selected.
Nothing — Does not display any MULTI windows or icons in the AltTab list.

When selecting the organizer in the Alt-Tab list

Determines what occurs after you select the MULTI icon in the AltTab list. Permitted settings for this option are:

Go to the last activated window (taskbarGotoLastWindow on) — Returns focus to the last active MULTI window.
Show a list of all windows (taskbarGotoLastWindow off) — Displays a shortcut menu providing access to all open MULTI windows. For more information, see "Taskbar Organizer Menu Options" in the MULTI: Building Applications book for your target.

Linux/Solaris only

Permitted settings for this option are:

on — [default] The vertical bar cursor in various windows (such as the Debugger command pane and the Editor) will blink.
off — The cursor will be a solid non-blinking bar.

Removes all of the key bindings so they can be created from scratch with keybind.

Removes all menus so they can be created from scratch using menu.

Removes all mouse button bindings so they can be created from scratch with the mouse command.

Linux/Solaris only

Specifies the length of time, in time tenths of a second, that MULTI waits between successive button presses to recognize double or triple clicks. For example, if time is 4, two clicks on the same button, in the same mouse location, within four tenths of a second, are treated as a double-click. If the two clicks are separated by more than time tenths of a second, they are treated as two single-clicks.

If no mouse binding requiring multiple clicks exists for a particular mouse location, MULTI executes the mouse binding immediately without waiting for multiple clicks.

The default time is 4.

Used within a configuration file to read in another configuration file specified by filename. After filename is processed, processing of the original configuration file continues as normal.

This option is deprecated. It does not control disassembly style.

Linux/Solaris only

Controls whether existing windows are automatically given focus when they are raised. This option does not affect windows when they are displayed for the first time.

on — [default] Existing windows are automatically given focus when they are raised. This setting is recommended if your window manager uses a click-to-focus policy.
off — Existing windows are not given focus when they are raised. This setting is recommended if your window manager uses a focus-follows-mouse policy.

Linux/Solaris only

Specifies an interval used to force processes to release any X-server keyboard or mouse grabs:

If time is less than zero — MULTI does not check to see if there are any outstanding grabs on the X-server each time it stops.
If time is greater than zero — MULTI checks to see if the process has any outstanding grabs when the process is stopped by a signal or breakpoint. If both the keyboard and the mouse are grabbed, MULTI waits time seconds before aborting the other process's grabs, and then exits.

The default time is -1.

This option is only useful for Solaris native and Linux native development.

Linux/Solaris only

Permitted settings for this option are:

on — The next MULTI window will be minimized as an icon when it opens.
If you repeatedly configure this option to on, it will remember the number of times you have done this, and cause the next num windows to be created minimized (one per time you configure the option to on). After the correct number of windows come up minimized, this option resets itself to off.
off — [default] Does not minimize MULTI windows.

This option is only applied to the next window created and does not affect existing windows.

Specifies the number of pixels the mouse can move during a press and release of a mouse button.

If you move the mouse less than num pixels between a button press and release, the click is treated as a single click. If you move the mouse more than num pixels between press and release, the mouse click is no longer treated as a single click but as two independent press and release events.

The default num is 4.

Linux/Solaris only

When you iconify a window, string prefixes the icon name. For example, if you set string to MULTI, iconified Editor windows are named MULTI:Filename.c instead of Filename.c.

If your window manager does not support iconifying, this option has no effect. The default is an empty string.

Changes to this setting only affect new windows.

Linux/Solaris only

Prepends string to the title bar's window name. The default is an empty string.

Changes to this setting only affect new windows.

Linux/Solaris only

Permitted settings for this option are:

on — If the windows manager supports this setting, all windows appear without title bars.
off — [default] Windows appear with title bars.

Specifies a character (string) used to break up large numbers for ease of reading. For example, specifying an underscore would cause MULTI to display 0x123456789 as 0x1_23456789.

string may only be a single character. The default is an empty string, which results in MULTI not using any separator character to break up numbers.

Permitted settings for this option are:

on — The full grep command prints out whenever the grep command is executed.
off — [default] The full grep command does not print out.

Linux/Solaris only

Permitted settings for this option are:

on — Enable synchronous X-windows mode. Synchronous mode ensures that X-window calls from MULTI complete before they return. This can be useful when running MULTI on faulty X-servers.
off — [default] Disables synchronous X-windows mode.

Permitted settings for this option are:

on — MULTI allows the window manager to determine where all windows should go.
off — [default] MULTI automatically places windows in convenient locations.

Open build details window*

Permitted settings for this option are:

Always (showProgress always) — The Build Details window opens every time you build an application, even if no warnings or errors are produced.
On Warnings and Errors (showProgress on warnings and errors) — [default] The Build Details window opens if your build produces warnings or errors.
On Errors (showProgress on errors) — The Build Details window opens if your build produces errors, but does not open for warnings.
Never (showProgress never) — The Build Details window never opens, even if warnings or errors are produced.

Automatically open editor on errors

Permitted settings for this option are:

Selected (autoEditErrors on) — [default] If the Build Details window is open or is configured to open on errors, the code that caused the first error of the build is automatically displayed in an Editor window.
Cleared (autoEditErrors off) — Errors are displayed in the Build Details window. Double-click an error to open it in an Editor window.

On warnings

Permitted settings for this option are:

Selected (autoEditWarnings on) — If the Build Details window is open or is configured to open on warnings, the code that caused the first warning of the build is automatically displayed in an Editor window.
Cleared (autoEditWarnings off) — [default] Warnings are displayed in the Build Details window. Double-click a warning to open it in an Editor window.

Use MULTI Editor on errors (even if alternate editor is specified elsewhere)

Permitted settings for this option are:

Selected (alwaysUseMeToFixBuildErrors on) — [default] Errors and warnings will be displayed in the MULTI Editor even if you have configured the MULTI environment to use an alternative, third-party editor.
Cleared (alwaysUseMeToFixBuildErrors off) — Errors and warnings will be displayed in the editor you use in your MULTI environment.

Project directory root

(defaultNpwDir string) Specifies the base directory where new projects are created. If left blank, new projects are created at:

Windows 8/Windows 7/Vista — C:\Users\username\My Documents\My Projects\
Windows XP — C:\Documents and Settings\username\My Documents\My Projects\
Linux/Solaris — ~/MyProjects/

The Project Wizard creates a Projectn directory in this location to act as the root directory of the project.

Parallel Build*

(buildType parallel) [default] Builds programs using the number of processes specified. See the descriptions of Number of parallel processes, Auto-detect, and Custom below.

Number of parallel processes*

(numParallelBuildProcesses num) Specifies the number of processes that may be run in parallel. This option is only available with the Parallel Build option. The default num is 2. See the descriptions of Auto-detect and Custom below.

Auto-detect*

(autoDetectNumParallel auto) [default] Auto-detects the maximum number of processes that may be run in parallel.

Use lock files (-lockout)*

Permitted settings for this option are:

Selected (useLockFiles on) — Prevents multiple simultaneous builds of the same program or library by creating temporary .lck lock files.
Cleared (useLockFiles off) — [default] Does not create temporary .lck lock files.

Note:-lockout is the corresponding gbuild option. For information about the gbuild utility program, see the MULTI: Building Applications book for your target processor family.

Execute tools at low priority (-nice)*

Permitted settings for this option are:

Selected (useLowPriority on) — Executes the build with lower than normal priority—scheduling priority 10 (Linux/Solaris) or the idle priority class (Windows).
Cleared (useLowPriority off) — [default] Executes the build at normal priority.

Note:-nice is the corresponding gbuild option. For information about the gbuild utility program, see the MULTI: Building Applications book for your target processor family.

Show tool commands (-commands)*

Permitted settings for this option are:

Selected (toolCommands on) — Displays commands as they are executed.
Cleared (toolCommands off) — [default] Does not display commands as they are executed.

Note:-commands is the corresponding gbuild option. For information about the gbuild utility program, see the MULTI: Building Applications book for your target processor family.

Beep when build completes

Permitted settings for this option are:

Selected (beepOnBuildCompletion on) — Beeps at the end of a successful build. This setting only takes effect if Allow beeping on the General tab is selected (see "The General Options Tab" in the MULTI: Building Applications book for your target).
Cleared (beepOnBuildCompletion off) — [default] Does not beep.

Automatically share target connections

Permitted settings for this option are:

Selected (autoConnectionMode on) — [default] The primary target connection is used.
Cleared (autoConnectionMode off) — Multiple target connections can run concurrently. Advanced users who need to have multiple target connections running must clear this option before starting multiple connections.

Display connection type in Connection Chooser

Permitted settings for this option are:

Selected (displayConnectionTypeinChooser on) — The type of a connection method is displayed in brackets after the name in the drop-down list in the Connection Chooser dialog. Custom connection methods have no type displayed.
Cleared (displayConnectionTypeinChooser off) — [default] Only the name of the connection method is displayed.

Ask before halting to set breakpoint

Permitted settings for this option are:

Selected (verifyHalt on) — [default] The Debugger will ask for confirmation before halting the process to set a breakpoint.
Cleared (verifyHalt off) — The Debugger will automatically halt, set the breakpoint, and continue the process without requiring user intervention.

Use function relative line numbers (vs. file relative)

Permitted settings for this option are:

Selected (procRelativeLines on) — [default] Debugger commands, such as the e command, interpret line numbers as function relative, instead of file relative.
Cleared (procRelativeLines off) — Line numbers are treated as file relative.

For more information, see Specifying Line Numbers.

Display all numbers/characters as hex

Permitted settings for this option are:

Selected (hexMode on) — All numeric values evaluated by the Debugger are displayed in hexadecimal format.
Cleared (hexMode off) — [default] Display format is based on the natural display format for that type. For integral types, the natural display format is decimal.

View unsigned char as integer

Permitted settings for this option are:

Selected (viewUnsignedCharAsint on) — [default] The natural display format of unsigned chars will be the same as for ints. This is useful when you want to view byte values as numeric values instead of characters.
Cleared (viewUnsignedCharAsint off) — The natural display format for unsigned chars is a literal character, such as 'A'.

Coloring for multiple debuggers

Specifies how the background color of new Debugger windows is chosen. It is useful to turn this on when using multiple Debugger windows to make them visually distinct. Permitted settings for this option are:

Do Not Color (backgroundMode off) — All Debugger windows use the normal background color.
Use Color Offsets (backgroundMode offset) — [default] New Debugger windows will use predetermined offsets from the normal background color. This option is usually best since it will pick colors near the current background color, and keep the text as legible as possible.
Use Preset Colors (backgroundMode preset) — New Debugger windows will use a color from a set of pre-chosen, highly distinctive colors.

Line numbers in source pane

Specifies how line numbers are displayed on the left side of the Debugger source pane. Permitted settings for this option are:

No Number (lineNumberMode none) — No line numbers are displayed.
File Number (lineNumberMode file) — The file relative line numbers are displayed.
Func Number (lineNumberMode func) — The function relative line numbers are displayed.
Both Numbers (lineNumberMode both) — [default] Both file-relative and function-relative line numbers are displayed.

Show variable values in tooltips

Permitted settings for this option are:

Never (fastest and safest) (hoverValues never) — Never show variable values in tooltips.
On Mouse Hover (hoverValues always) — When the mouse is positioned over a variable, show its value in a tooltip.
On Mouse Hover with Shift Key (hoverValues onShift) — [default] When the mouse is positioned over a variable and the Shift key is pressed, show the variable's value in a tooltip.

Variables are evaluated in the context of the blue current line pointer. If you want to view the value of a local variable, ensure that the current line pointer is positioned in the current function.

Debugger child windows

Windows only

Controls how Debugger child windows (such as the Data Explorer and the Breakpoints window) interact with the Debugger window in terms of stacking order. Permitted settings for this option are:

Stay above Debugger (viewsAreChildrenMode children) — [default] Child windows are always displayed in front of the Debugger. This makes it easy to keep track of child windows, but can be annoying if the child windows start to obscure the Debugger window. Child windows can be minimized, but this mode precludes partially obscuring a child window with the Debugger to save space.
Can be below Debugger (viewsAreChildrenMode topLevel) — Child windows can be either above or below the Debugger. This allows child windows to overlap, which makes it easier for you to work if you have a smaller display or if child windows take up a large portion of your screen.
Are initially focused (viewsAreChildrenMode keepFocus) — This option is deprecated. Use Can be below Debugger instead.

Changes to this option setting only affect subsequently opened windows, not pre-existing windows.

Command pane prompt

(prompt string) Specifies the string used as a prompt in the Debugger command pane to indicate that user input is desired. The default string is MULTI>.

Configure Debugger Buttons

Opens a dialog box that you can use to edit the Debugger toolbar buttons. This dialog box is only accessible from the MULTI Debugger. For more information, see Adding, Removing, and Rearranging Toolbar Buttons.

Minimum initial size (WxH)

(minViewSize widthxheight) Specifies the minimum initial size that will be used to auto-size Data Explorer windows in characters (width) by lines (height) or in pixels, as specified.

The default widthxheight is 40x3. The default units are characters/lines. To specify pixels from the command pane or in a configuration file, put a p after widthxheight (for example, 200x21p).

Maximum initial size (WxH)

(maxViewSize widthxheight) Specifies the maximum initial size that will be used to auto-size Data Explorer windows in characters (width) by lines (height) or in pixels, as specified.

If the minViewSize option (preceding) is greater in either dimension than maxViewSize, the maxViewSize value is still used.

The default widthxheight is 40x40. The default units are characters/lines. To specify pixels from the command pane or in a configuration file, put a p after widthxheight (for example, 200x200p).

Initial position (XxY)

(firstPosition x-coordinatexy-coordinate) Specifies the initial position of the Data Explorer from the top-left of the screen. You may specify the position in characters (x-coordinate) by lines (y-coordinate) or in pixels.

This option only applies to the first Data Explorer. Subsequent Data Explorers are offset from the first one that was created, preventing excessive overlap. If this option is left unspecified (blank), the Data Explorer remembers its previous position. The default x-coordinatexy-coordinate is 0x0. The default units are characters/lines. To specify pixels from the command pane or in a configuration file, put a p after x-coordinatexy-coordinate (for example, 0x0p).

Automatically dereference pointers

Permitted settings for this option are:

Selected (derefPointer on) — [default] MULTI automatically follows pointers when it encounters them and prints both the pointer value and the object it points to.
Cleared (derefPointer off) — MULTI only displays the value of the pointer.

Check syntax of breakpoints when they are set

Permitted settings for this option are:

Selected (bpSyntaxChecking on) — [default] Commands associated with a breakpoint must pass syntax checking for the breakpoint to be set. Breakpoint commands that fail syntax checking cannot be set.
Cleared (bpSyntaxChecking off) — A syntax error in a breakpoint command will not be detected by MULTI until the breakpoint is hit and MULTI tries to execute the associated commands.

Continue running script files on error

Permitted settings for this option are:

Selected (continuePlaybackFileOnError on) — The Debugger will not stop if it encounters an error while running a script file. Instead, it will print any error output and continue reading and performing commands out of that file.
Cleared (continuePlaybackFileOnError off) — [default] The Debugger aborts running a script file if it encounters an error.

“s” (step) and “n” (next) are blocking by default

Permitted settings for this option are:

Selected (blockStep on) — Step/next operations block subsequent commands until the step/next operations have finished.
Cleared (blockStep off) — [default] Step/next operations allow subsequent commands to execute before the step/next operations have finished.

You can make a step or next command blocking or non-blocking regardless of the setting of this option by appending an n (for non-blocking) or b (for blocking) to the command. See Single-Stepping Commands.

See also .

Stepping over longjmps

When the Debugger performs a next operation over a subroutine that calls longjmp or throws a C++ exception (implemented by a call to longjmp internally), the subroutine does not return in the normal way because of the transfer of control within the function call. This is significant because the Debugger uses a temporary breakpoint just after the normal return address to implement the next operation. This is also true of step if there is no source available for the subroutine. When longjmp is called, this temporary breakpoint is bypassed because of the transfer of control, and execution can run away since the breakpoint will never be hit.

This configuration option controls how MULTI attempts to properly catch unexpected transfers of control while stepping through code. Permitted settings for this option are:

Ignore/Run Away (longjmpStepMode ignoreRunAway) — [default] Allows the code to call longjmp without attempting to detect abnormal transfers of control.
Minimize Temp Stops (longjmpStepMode minimizeTempStops) — Fixes the problem in a way that does not cause temporary stops in longjmp as the process runs normally. This option inserts and removes a temporary breakpoint at longjmp for each next over a function call.
Maximize Step Speed (longjmpStepMode maximizeStepSpeed) — Fixes the problem in a way that minimizes the time it takes to do a next. This option leaves a permanent breakpoint at longjmp and results in execution always halting due to a breakpoint being hit whenever the process calls longjmp—even during normal execution.

Debug server timeout in seconds

(serverTimeout seconds) Specifies the number of seconds to wait for communication from a debug server before assuming it is dead and disconnecting from it.

A timeout that is too low may cause a premature disconnect from the debug server, and is not recommended. A fairly high timeout can be useful for very slow debug servers or for debug servers that are being debugged. However, a high timeout can be frustrating if the debug server dies because the Debugger cannot accept input while it's waiting for communication from the debug server.

The default is 15 seconds.

Interval to refresh Task Manager (in seconds)

(serverPollinterval seconds) Specifies the polling interval in seconds. MULTI checks for interesting events happening in the underlying RTOS and refreshes the Task Manager periodically.

The default is 5 seconds.

Criteria to decide if a task is in a group

Controls how to match a task fingerprint against a task. For more information about how the fingerprint is used in the construction process of a task group, see Run-Mode Debugging.

Permitted settings for this option are:

Task Name (taskMatchCriteria name) — [default] Matches against the name of the task.
Task Identifier (taskMatchCriteria id) — Matches against the identifier of the task.
Task Name or Identifier (taskMatchCriteria nameOrid) — Matches against the name or identifier of the task.

Prompt when exiting Debugger

Controls whether a confirmation dialog box appears when a user attempts to close the Debugger. Permitted settings for this option are:

Confirm If Process Started (promptQuitDebugger normal) — [default] The confirmation dialog box is displayed only if the Debugger is attached to a process that has been started. If the Debugger is attached to a process that has not been started, the Debugger closes without displaying the confirmation dialog box. In a run-mode debugging environment, the Debugger closes without displaying the confirmation dialog even though the process has been started.
Always Confirm (promptQuitDebugger always) — The Debugger will not close until the user confirms the action in the confirmation dialog box.
Never Confirm (promptQuitDebugger never) — The Debugger never displays the confirmation dialog box before closing.

Maximum size for container display

(maxContainerDisplaySize num) Sets the maximum number of elements initially displayed when a container is viewed in a Data Explorer.

The default num is 20.

Increment to maximum container size

(containerSizeincrement num) Sets the number of elements to add when expanding a container that is being viewed in a Data Explorer.

The default num is 10.

on — Stepping and execution of command line function calls are allowed from within a breakpoint command. This is somewhat risky because infinite breakpoint command recursion can occur if the execution from within the breakpoint command causes the same or another breakpoint to be hit. The resume command is always allowed in a breakpoint command.
off — [default].

on — [default] Permits command line function calls during evaluation of an expression as part of an examine command. Clicking an expression in the Debugger's source pane automatically executes an examine command, so when this option is enabled (the default), clicking an expression can trigger a function call.
off — Disallows command line function calls during evaluation of an expression. When this option is disabled, clicking an expression that involves a function call will result in a warning message.

on — Permits command line function calls via a freeze-mode connection to an operating system kernel if the OSA master process is selected in the target list. This may lead to overwritten register values and may only be safe if no code on your target uses floating-point registers, vector registers, or other extended registers, or if your target CPU does not have these registers. Note that this option setting does not permit command line function calls if an OSA task is selected in the target list.
off — [default] Disallows command line function calls via a freeze-mode connection to an operating system kernel.

on — [default] Skips checks related to instrumentation toggling. If the instrumentation on the target has been modified prior to the current run-mode connection being established, the contents of the History window are undefined.
off — Does not skip checks related to instrumentation toggling. Disabling this option may cause a delay when you open History or run backwards for the first time after the system is paused.

on — Outputs auto-translated debug information to the same directory as the executable that generated the debug information. For example, if your program is C:\myProgram, output will be sent to C:\. Existing debug information files may be overwritten without prompting.
off — [default] Outputs auto-translated debug information to a temporary directory.

See the related configuration options autoDwarf2Dbo and autoStabs2Dbo.

on — Run/continue operations block subsequent commands until the target has halted again. When the Debugger is blocking input, you will not be able to issue Debugger commands, or interact with Debugger buttons, windows, or menus. You can regain control by hitting the Esc key to abort the run/continue operation.
off — [default] Run/continue operations allow subsequent commands to execute before the target has halted again.

See also Run Commands, Continue Commands, and the blockStep option.

Removes all the Debugger buttons (except for the Close Debugger button if it is present) so that you can create them from scratch with the debugbutton command (see "Configuring and Customizing Toolbar Buttons" in the MULTI: Building Applications book for your target) or the Customize Toolbar window (see Adding, Removing, and Rearranging Toolbar Buttons).

on — [default] Single-clicking a breakdot sets an any-task breakpoint.
off — Single-clicking a breakdot sets a task-specific breakpoint.

For targets that do not support any-task or task-specific breakpoints, these settings are equivalent.

Sets the maximum number of scroll back lines available in the Cmd, Trg, I/O, Srl, Py, and Tfc panes.

If a MULTI session is in use for a long period of time, these panes can use a large amount of memory. Setting this option to a smaller value reduces memory usage, but also limits the number of available scroll back lines.

The valid range for num is 10 to 10485760. The default num is 10240.

Lists the defined Debugger buttons. See also "Configuring and Customizing Toolbar Buttons" in the MULTI: Building Applications book for your target.

The download window shows the current progress of a program download. Permitted settings for this option are:

on — [default] The download window will be used when downloading a program to the debug server.
off — The download window will not be used.

on — When executing from a script file, Debugger commands being executed will be displayed.
off — [default] When executing from a script file, Debugger commands being executed will not be displayed.

Limits the depth to which nested structs are displayed in a Data Explorer.

The valid range for num is 1 – 128. The default num is 128.

Limits the length of the value displayed in each row of a Data Explorer. For example, if this is set to 2000, only the first 2000 characters of a string will display, followed by ... to indicate there are more characters that are not displayed. Data values displayed in a single row in a Data Explorer can be very long (when displaying a long string value or a structure with many nested structs, for example).

The valid range for num is 1024 to 10 megabytes (10485760). The default num is 8192.

Sets the size and position of the Debugger window, where:

width and height — Correspond to the pixel size of the Debugger window.
x_offset and y_offset — Are optional values that indicate the pixel offset at which the Debugger window appears from the top-left corner of the screen for the + variant or from the bottom-right corner of the screen for the - variant. For example, the entry: geometry 500x700+0+0 specifies a 500-pixel-wide by 700-pixel-high Debugger window that appears in the top-left corner of the screen.

The defaults depend on screen size and vary from system to system. The width is approximately wide enough to display 80 characters on a line.

Changes to this option affect new Debugger windows, but not currently open windows.

on — Enables the global scope entry in the Browse window.
off — [default] Disables global scope entry in the Browse window.

This option corresponds to the Tools-->Global Scope On/Off menu item in the Browse window. See Headings in the Functions Browse Window.

Changes to globalHeading affect new Browse windows, but not currently open windows.

on — If you are using the Debugger command g, any breakpoint at the destination will be hit as soon as execution begins at the new location.
This option also controls whether a breakpoint set on the first instruction of a function called from the command line is hit.
off — [default] The breakpoint will not be hit.

This option specifies how many commands to remember for the Debugger command history mechanism. For more information, see History Commands.

The default num is 256.

Linux/Solaris only

Specifies the dimensions (ignored by some window managers) for the icon that is used when the Debugger is minimized, where:

width and height — Are the width and height of the icon in pixels.
x_offset and y_offset — Specify the number of pixels that the icon should be offset from the top-left corner of the screen.

The defaults are 32x64+0+0.

Permitted settings for this option are:

on — [default] The value of an expression is echoed when the expression is entered into the command pane.
off — The value of an expression is not echoed when the expression is entered into the command pane.

Note: This option affects expression evaluation in the %EVAL{commands} sequence used with the substitute command.

Controls whether output from Debugger panes other than the command pane (Cmd) will also be output to the command pane. Permitted settings for this option are:

on — [default] Output from Debugger panes other than the command pane will be output to the command pane. For example, I/O pane output will show up in the command pane with the prefix I/O:.
off — Output from other panes will not appear in the command pane.

Controls whether the History log is cleared when you unload an application from the target. Permitted settings for this option are:

on — [default] Unloading an application from the target clears the History log. This is equivalent to unloading the application, waiting for the unload to complete, and then issuing the Debugger command history -invalidate. This option setting prevents multiple instances of an application from being displayed in History after you reload the application.
Note that the History log may contain data used by the History window and by INTEGRITY TimeMachine.
off — Unloading an application from the target does not clear the History log.

By default, when the Debugger opens a Data Explorer or monitor window with useWmPositioning off, the new window is stacked on top of previous windows to save screen space. This option leaves the top num lines of the previous window visible.

The default num is 4.

Limits the number of lines of output generated by expression printing commands and the l command. When set to 0, the number of lines of output is unlimited.

The valid range for num is 0 to 2147483647. The default num is 4096.

Controls whether all OSA tasks appear in the target list. Permitted settings for this option are:

on — [default] Displays all OSA tasks in the target list when the OSA Explorer is open.
off — Does not display all OSA tasks in the target list. A subset of OSA tasks may appear if accessed by the trace analysis tools.

Controls whether the Debugger automatically displays the currently executing user-mode task when the kernel is stopped while executing user-mode tasks.

Permitted settings for this option are:

on — [default] Automatically displays the currently executing user-mode task.
off — Does not display the currently executing user-mode task.

Specifies the maximum number of OSA tasks loaded from trace data that are automatically displayed in the target list. This option does not limit the number of OSA tasks that can be added to the target list by your request. For example, the configured number may be exceeded if:

You open the OSA Explorer.
The target halts in a user-mode task that is not displayed in the target list, and the configuration option osaSwitchToUserTaskAutomatically is set to on (the default).

The default num is 32.

Note: This option is deprecated.

Permitted settings for this option are:

on — Forces hexadecimal values to be displayed padded to their full width with zeros. For example, a four-byte variable with a value of 0x8 is displayed as 0x00000008.
off — [default] Hexadecimal values are displayed without leading zeros.

This option has no effect on the padding of hexadecimal values printed in the command pane.

Note: This option is deprecated. We recommend that you instead use one of the methods described in .

Permitted settings for this option are:

on — When you prepare a single core of a multi-core target (for example, via the prepare_target command), MULTI automatically prepares each remaining core as if you had run prepare_target -verify=none on the executable associated with it. (This is equivalent to choosing the Prepare Target dialog option Program already present on target. Verify: Not at all for each remaining core.) For more information, see Preparing Multiple Cores to Run a Single Executable.
off — [default] Each core of a multi-core target is treated independently when you prepare the target.

When the current line pointer is in an inner block of a function and that inner block defines a variable that has the same name as a variable in the outer block, a function qualified reference to the name of the variable can either refer to the variable of that name in the outermost block or to the variable of that name in the current inner block. This option determines which of the two variables is used. Permitted settings for this option are:

on — The variable in the outermost block is used.
off — [default] The variable in the current inner block is used.

Permitted settings for this option are:

on — The tog command does not echo the status of the breakpoint(s) it toggles.
See also the q option for the tog command.
off — [default].

When command recording is enabled, commands executed from script files are recorded as comments. This option controls whether commands executed from macros are also recorded as comments. Permitted settings for this option are:

on — Commands executed from macros are recorded as comments.
off — [default] Commands executed from macros are not recorded as comments.

Permitted settings for this option are:

on — [default] Runs script files as usual when an executable is opened in the Debugger. See "Using Script Files" in the MULTI: Building Applications book for your target.
off — Only runs command line script files (that is, those explicitly specified on the command line with -rc) when an executable is opened in the Debugger. This setting is equivalent to the -norc command line option. See also the -rc and -norc command line options.

on — [default] MULTI sets a breakpoint at the starting routine of a program when the process is run. Execution is resumed automatically when this breakpoint is hit unless a user breakpoint was set at the same spot. This is necessary to prevent corrupted call stack traces.
off — MULTI does not set a breakpoint at the starting routine of a program when the process is run.

on — [default] MULTI attempts to debug shared objects.
off — MULTI does not attempt to debug shared objects.

Permitted settings for this option are:

on — [default] On Linux/Solaris, and if MULTI is running in the background, the shell command opens a dialog box that allows you to confirm or cancel execution of the shell command. This is helpful when MULTI is running in the background because shell commands have no accessible standard output or standard error.
On Windows, the command window waits to be dismissed after running the shell command.
off — On Linux/Solaris, MULTI always executes shell commands immediately, without opening the dialog box.
On Windows, the command window exits immediately after running the shell command.

Permitted settings for this option are:

on — The Debugger automatically kills any existing process and reloads the symbols without displaying a dialog box. This is useful if you are using a Debugger primarily to examine symbols and not to debug running processes.
off — [default] When the executable open in the Debugger changes, the Debugger displays a dialog box asking if any existing process should be killed and the symbols reloaded.

Controls whether the c (continue) command in a breakpoint is ignored during a single-step operation (but not during a run operation).

Note: This option determines whether a continue command is ignored, not a resume command.

Permitted settings for this option are:

on — MULTI ignores the c command in the breakpoint command list, prints a warning, and stops the process at the breakpoint.
off — [default] MULTI does not ignore the c command in the breakpoint command list. For example, if you have a breakpoint with the command list print x; c and you step on to this breakpoint, the process starts running because the c command causes the process to continue. The c command inside a breakpoint always causes the process to start running, which is not the desired behavior if you want to step on to that line.
Note that the resume command should be used inside breakpoint command lists. If the breakpoint's command list is print x; resume, the process stops when you step on to the breakpoint. If the process runs and hits the breakpoint, it will keep running (the process resumes whatever it was going to do before hitting the breakpoint).

Controls whether the Debugger automatically switches to a task that is not currently selected in the target list when a breakpoint is hit in that task. Permitted settings for this option are:

on — [default] When a breakpoint is hit in a task that is not currently selected in the target list, the Debugger automatically switches to that task if no other Debugger window is open on it and if the currently selected task is not halted. Switching occurs for both software and hardware breakpoints.
off — The Debugger does not automatically switch to a task when a breakpoint is hit in that task.

Specifies the background color (commands end with Bg) or foreground color (commands end with Fg) for Tree Browser displays, where:

Type is one of the following:
- FunctionNormal (tbFunctionNormalBg and tbFunctionNormalFg) — Functions displayed in the static call Tree Browser which have debugging information.
- FunctionNoinfo (tbFunctionNoinfoBg and tbFunctionNoinfoFg) — Functions displayed in the static call Tree Browser which do not have debugging information.
- FunctionRecursive (tbFunctionRecursiveBg and tbFunctionRecursiveFg) — Functions displayed in the static call Tree Browser that may be recursive.
- FunctionAdrTaken (tbFunctionAdrTakenBg and tbFunctionAdrTakenFg) — Nodes representing the possibility of calls to a function through function pointer in a Tree Browser.
- DynNormal (tbDynNormalBg and tbDynNormalFg) — Functions displayed in the dynamic call Tree Browser with debugging information.
- DynNoinfo (tbDynNoinfoBg and tbDynNoinfoFg) — Functions displayed in the dynamic call Tree Browser without debugging information.
- FileNormal (tbFileNormalBg and tbFileNormalFg) — Files displayed in the file call Tree Browser with debugging information.
- FileNoinfo (tbFileNoinfoBg and tbFileNoinfoFg) — Files displayed in the file call Tree Browser without debugging information.
- ClassUnion (tbClassUnionBg and tbClassUnionFg) — Unions displayed in the class Tree Browser.
- ClassStruct (tbClassStructBg and tbClassStructFg) — Types displayed in the class Tree Browser with debugging information.
- ClassNoinfo (tbClassNoinfoBg and tbClassNoinfoFg) — Types displayed in the class Tree Browser without debugging information.
- ClassClass (tbClassClassBg and tbClassClassFg) — Class data types displayed in the class Tree Browser.
- ClassEnum (tbClassEnumBg and tbClassEnumFg) — Enum data types displayed in the class Tree Browser.
Bg or Fg — Specifies whether you are changing the background or foreground color of the displayed items.
color — Specifies the new color in RGB format. For more information, see "Colors Configuration Options" in the MULTI: Building Applications book for your target.

Specifies how new Data Explorer entries will be displayed. Note that you can override many of these default display settings on a per-entry basis in the Data Explorer. For more information, see .

Permitted settings for this option are:

number_option can be one of the following:
- NaturalOrHex — Numbers display in their default states unless hexMode on is set (see "The Debugger Options Tab" in the MULTI: Building Applications book for your target).
- Natural — Numbers display in their default states.
- Hex, Decimal, Oct, or Binary — Numbers and characters display in base 16, base 10, base 8, or base 2 notation, respectively.
eval_option specifies how the Debugger re-evaluates expressions when updating Data Explorers, and can be one of the following:
- ReEvaluate — Each expression is re-evaluated in the same context as when the Data Explorer displaying it was first created.
- ReEvalContext — Expressions are re-evaluated within the current function at the top of the call stack.
- ReEvalinGlobal — When expressions are re-evaluated, only looks for variables in the global scope.
- UseAddress — Uses last valid address of variables being displayed.
other_options can include any of the options listed below. (Prepending an option with a dash (-) disables the behavior.)
- ShowAddress — This option is deprecated.
- ShowFType — This option is deprecated.
- Alternate — Displays data in an alternative format, if available.
- PadHex — Adds zeros to the left of hexadecimal numbers to maintain same bit width, as needed. (Otherwise, only nonzero hexadecimal digits display.)
- ShowBases — Displays the base classes of a C++ class along with a derived instance.
- ShowAllFields — This option is deprecated.
- ShowDerived — Determines the most derived C++ class type of the current object and redisplays the object cast to that type.
- ExpandValue — This option is deprecated.
- ExpandComplexMemberValue — This option is deprecated.
- OpenPointer — This option is deprecated.
- ShowChanges — This option is deprecated.

The defaults are NaturalOrHex ReEvalContext -ShowAddress -ShowFType -Alternate -PadHex ShowBases -ShowAllFields ShowDerived ExpandValue ExpandComplexMemberValue OpenPointer ShowChanges.

Permitted settings for this option are:

on — The Debugger displays a warning before replacing a pre-existing breakpoint with a new breakpoint. This can help prevent the accidental loss of breakpoints with long command lists.
off — [default] The Debugger does not warn you before replacing a pre-existing breakpoint.

Permitted settings for this option are:

on — The Debugger displays a warning when setting a breakpoint on a line with no corresponding assembly code.
off — [default].

Reuse editor windows

Permitted settings for this option are:

Selected (openFilesinNewBuffers on) — The first file opened from a MULTI executable such as the Project Manager or Debugger opens in a new Editor window. Subsequently opened files reuse the Editor window initially opened from the MULTI executable.
Cleared (openFilesinNewBuffers off) — [default] Every file opens in a new Editor window.

Create backup files when saving

Permitted settings for this option are:

Selected (editorBackups on) — A backup of the on-disk version of a file will automatically be created before saving over it. The backup file has the same name as the original file, with a tilde (~) appended to it.
Cleared (editorBackups off) — [default] Backup files will not be created.

Allow middle click to paste

Permitted settings for this option are:

Selected (allowMiddleClick on) — [default for Linux/Solaris] Clicking the middle mouse button will have the same effect as pasting from the selection buffer.
Cleared (allowMiddleClick off) — [default for Windows] Clicking the middle mouse button will not paste from the clipboard.

Enter spaces in place of tabs

Permitted settings for this option are:

Selected (tabsAreSpaces on) — Tab characters entered into an Editor window will be replaced by an appropriate number of space characters in the Editor buffer, regardless of whether the Tab is the result of pressing Tab, entering a paste command, or auto indenting in the Editor.
Cleared (tabsAreSpaces off) — [default] Space characters are not inserted in place of Tab characters.

Drag and drop text editing

Permitted settings for this option are:

Selected (dragAndDrop on) — Text can be moved in the Editor by selecting a block of text and dragging the mouse to a new location.
Cleared (dragAndDrop off) — [default] Text cannot be moved by dragging the mouse.

Allow overtype mode

Permitted settings for this option are:

Selected (allowOvertypeMode on) — Allows switching between insert and overtype mode.
Cleared (allowOvertypeMode off) — [default] Does not allow switching between insert and overtype mode.

Tab size

(tabSize spaces) Specifies the number of spaces used to display a Tab in the Editor. The default is 8 spaces.

Indent size

(editindent spaces) Specifies the number of spaces in an indentation. The default is 4 spaces.

Ctrl+cursor jump size

(editSomeSize num) Specifies the value used by the UpSome, DownSome, LeftSome, and RightSome Editor commands. For information about these commands, see "Navigation Commands" in the MULTI: Building Applications book for your target.

The default num is 5.

Configure Editor Buttons

Opens the Configure Editor Buttons dialog box, which allows you to edit the Editor buttons using the same format as the editbutton command. The dialog box lists currently defined buttons on the left, and available icons on the right.

Auto indent as you type

Permitted settings for this option are:

Selected (aiimplicitindent on) — [default] The Editor automatically indents the file as you type.
Cleared (aiimplicitindent off) — The Editor will not automatically indent your file.

Only auto indent when typing first character in line

Controls auto indentation. This configuration option only takes effect if Auto indent as you type is selected.

Permitted settings for this option are:

Selected (aiimplicitOnlyAtinitial on) — [default] The MULTI Editor only automatically indents a line when the first typed character (includes space characters) is an auto-indent character. See "Auto-Indent Characters" in the MULTI: Building Applications book for your target.
Cleared (aiimplicitOnlyAtinitial off) — The MULTI Editor automatically makes indenting adjustments when you type auto-indent characters, regardless of where they appear on the line.

Auto indent comments as you type

Controls auto indentation in block comments. This configuration option only takes effect if Auto indent as you type is selected.

Permitted settings for this option are:

Selected (aiimplicitindentinComments on) — [default] Starting on the second line, block comments are automatically indented with additional spaces so that lines are aligned as you type.
Cleared (aiimplicitindentinComments off) — Block comments are not indented with additional spaces unless you auto indent them.

Double indent size when indenting body of switch

Permitted settings for this option are:

Selected (aiSwitchinTwo on) — [default] For C or C++ source files, switch bodies are indented two levels so that case labels are indented one level from the switch. For Ada source files, select bodies are indented two levels so that labels are indented one level from the select.
Cleared (aiSwitchinTwo off) — For C or C++ source files, the case labels are even with the switch. For Ada source files, the labels are even with the select.

Indent comments when indenting multiple lines

Permitted settings for this option are:

Selected (aiTouchComments on) — [default] Comments are indented when auto indenting multiple lines.
Cleared (aiTouchComments off) — Comments are only indented if you auto indent a single line.

Comments stick flush left

Permitted settings for this option are:

Selected (aiCommentsStayFlushLeft on) — [default] All comments will be kept directly on the left margin.
To indent a comment that is stuck to the left margin while this option is selected, insert a space just before the start of the comment, then auto indent the comment.
To move a comment to the left margin, regardless of the position where the comment started, insert a number sign (#) as the first character of a comment. For example, if you are coding in C, type: /*# and the comment is automatically moved to the left margin.
Cleared (aiCommentsStayFlushLeft off) — Indents will be applied to comments.

C chars aligned like '*' in comments

(aiCharsLikeStarinComment char_string) Allows characters other than asterisks (*) to line up in comments as if they were asterisks. The default char_string is - (dash).

The default setting allows correct automatic indentation of comments that have a column of - (dashes) down the left side, lined up under the * in the /* sequence. To have characters other than asterisks (*) line up in comments as if they were asterisks, make them part of the char_string.

C paren indent mode

Controls how the Editor indents a line in a C/C++ source file if it starts within an open parenthesis/close parenthesis pair. Permitted settings for this option are:

Even with parentheses (aiParenindentMode evenWithParen) — If there is a non-whitespace character between the open parenthesis and the end of its line, the lines enclosed in parentheses start at the same column as that character. Otherwise, the lines enclosed in parentheses start in the column just after the open parenthesis. For example:
```
void foo (void)
{
    bar(
        argument_one,
        argument_two
        );
}
```
Indent in two (aiParenindentMode indentinTwo) — [default] Lines enclosed in parentheses start two indent levels in from the line that contains the open parenthesis. For example:
```
void foo (void)
{
    bar(
            argument_one,
            argument_two
            );
}
```

Ada paren mode

Controls how the Editor indents a line in an Ada source file if it starts within an open parenthesis/close parenthesis pair. Permitted settings for this option are:

Even with parentheses (aiAdaParenindentMode evenWithParen) — [default] If there is a non-whitespace character between the open parenthesis and the end of its line, the lines enclosed in parentheses start at the same column as that character. Otherwise, the lines enclosed in parentheses start in the column just after the open parenthesis.
Indent in two (aiAdaParenindentMode indentinTwo) — The lines enclosed in parentheses start two indent levels in from line that contains the open parenthesis.

Print 2 columns if landscape orientation is selected

Windows only

Permitted settings for this option are:

Selected (editPrint2Column on) — The Editor prints files with two columns per sheet if landscape orientation is selected.
Cleared (editPrint2Column off) — [default] The Editor prints one column per sheet.

Temp file directory

(tempFileDir dirpath) Specifies the directory where MULTI stores its temporary files. The default is blank, which has the following results:

Windows — Uses the values of the TMP or TEMP environment variables and defaults to the current directory if those variables are not set.
Linux/Solaris — Uses the values of the TMPDIR or TEMP environment variables and defaults to /tmp if those variables are not set.

Initial width in characters

(editWidth width) Specifies the initial width of Editor windows in characters.

This option is only useful when Save window positions and sizes is cleared (rememberWindowPositions off). See the Save window positions and sizes option in "The General Options Tab" in the MULTI: Building Applications book for your target.

The default width is 80.

Initial height in characters

(editHeight height) Specifies the initial height of Editor windows in characters.

The default height is 32.

Selection margin width in pixels

(selectionMarginWidth num) Specifies the width of the Editor's left margin in pixels.

If the width is nonzero, you can click in the left margin to select the line to the right. Clicking in the margin and dragging up or down selects multiple lines. If the width is 0, you cannot select lines in this way, and the left margin does not appear. For an alternative selection method, see the description of triple left-clicking in "First (Left) Mouse Button" in the MULTI: Building Applications book for your target.

If the width is nonzero and the configuration option Show line number is selected (showLineNumberinEditor on), the width of the margin is adjusted as necessary to accommodate the line numbers that appear. For information about Show line number, see below.

The default num is 13.

Show line number

Permitted settings for this option are:

Selected (showLineNumberinEditor on) — [default] If Selection margin width in pixels (above) is set to nonzero (selectionMarginWidth nonzero_num), line numbers are displayed in the Editor's left margin. The width of the margin is adjusted as necessary to accommodate the line numbers.
If Selection margin width in pixels is set to 0 (selectionMarginWidth 0), line numbers are not displayed in the Editor's left margin.
Cleared (showLineNumberinEditor off) — Line numbers are not displayed in the Editor's left margin.

Generate auto-recover file every x seconds

(editincrFrequency num) Specifies the number of seconds between generation of auto-recover files.

The Editor will create an auto-recover file every num seconds as you edit. If the power goes out or the Editor crashes, the next time you open the same file, you will be given the option to re-apply the edits saved in the auto-recover file.

The default num is 1.

Spaces per indent for Ada

(adaindentSize num) Specifies the number of spaces in an indentation for Ada files. The default num is 3.

Ada continuation line indent

(adaContinuationSize num) Specifies the number of spaces in an indentation for a continuation line in Ada files. The default num is 2.

Word wrap

Permitted settings for this option are:

Selected (wordWrap on) — If lines are longer than the wrapping width, the Editor will automatically split lines on word boundaries as you type.
Cleared (wordWrap off) — [default] Lines will not wrap.

Wrap column

(wrapColumn width) When Word wrap is selected (wordWrap on), width specifies the last column a character can occupy before the Editor wraps to the next line.

The default width is 79.

Wrap indent offset

(wrapindent num) When a word wraps to the next line, the word is automatically indented num extra spaces from where it would normally appear. The default num is 2.

Fill paragraph column

(fillParagraphColumn num) Specifies the column at which each line will be wrapped when using CtrlShiftA to reformat comments.

The default num is 79.

This option is bound to the FillParagraph command (see "Block Commands" in the MULTI: Building Applications book for your target).

Controls whether the MULTI Editor automatically grabs function prototypes from a source file's include files when the source file is loaded.

on — [default] The MULTI Editor automatically grabs function prototypes when opening source files. This setting enables auto-completion of function names.
off — The MULTI Editor does not grab function prototypes when opening source files. This setting is recommended if you notice poor performance when this option is enabled.

Removes all Editor buttons so they can be created from scratch with the editbutton command.

Specifies whether or not to draw the wrap line in the MULTI Editor. Permitted settings for this option are:

on — [default] Enables the wrap line.
off — Disables the wrap line.
asWordWrap — Enables the wrap line if word wrap is enabled.

This option does the same thing as the Editor command DrawWrapLine.

Every time you type a right parenthesis, right square bracket, or right curly brace, the Editor briefly selects the matching one. The Editor will pause on this highlight of the previous match for time tenths of a second. A value of 0 (zero) will disable matching. The default time is 10.

Save command history between sessions

Permitted settings for this option are:

Selected (saveCommandHistory on) — [default] The command history for each executable will be saved. If the executable has not been debugged before, it will have no previous command history.
Cleared (saveCommandHistory off) — The command history will not be saved.

Save data explorers between sessions

Permitted settings for this option are:

Selected (saveViewWindows on) — Saves all variables being viewed in Data Explorers between MULTI sessions on the same executable. When restored, the variables are all added to one Data Explorer, or each is added to a different Data Explorer as dictated by the Reuse Data Explorer option.
Cleared (saveViewWindows off) — [default] Data Explorer contents are not saved.

Save arguments between sessions

Permitted settings for this option are:

Selected (saveRunArguments on) — [default] Saves the last arguments supplied to run the target program between MULTI sessions on the same executable. To run the executable with no arguments, use the R command.
Cleared (saveRunArguments off) — Arguments are not saved.

Remember software breakpoints

Determines whether the Debugger remembers software breakpoints (including shared object breakpoints) that you have set for a program the next time you debug the same program. Permitted settings for this option are:

Never (rememberBreakpoints never) — The Debugger clears all software breakpoints whenever you load or reload a program.
Across Reloads (rememberBreakpoints acrossReload) — [default] The Debugger remembers software breakpoints when you reload the program within a single session. Software breakpoints are lost when you exit MULTI.
Across Sessions (rememberBreakpoints acrossSessions) — The Debugger remembers software breakpoints even if you exit and restart MULTI.

Note: The Debugger may not remember group breakpoints and does not remember hardware breakpoints.

Restored breakpoints overwrite breakpoints set by scripts

Permitted settings for this option are:

Selected (overwriteScriptBreakpoints on) — Previously saved breakpoints will overwrite breakpoints that have been created by a script run automatically for the current executable.
Cleared (overwriteScriptBreakpoints off) — [default] Previously saved breakpoints will not overwrite breakpoints that have been created by a script run automatically for the current executable.

Remember base addresses (e.g. _TEXT)

Determines whether the Debugger remembers address offsets that you have set for a program the next time you debug the same program. This option is only applicable to programs that are compiled for use with position-independent code and/or position-independent data. Permitted settings for this option are:

Never (rememberBaseAddrs never) — The Debugger will clear all base addresses whenever you load or reload a program.
Across Reloads (rememberBaseAddrs acrossReload) — [default] The Debugger will remember address offsets that you have set when you reload the program within a single session. Address offsets are lost when you exit MULTI.
Across Sessions (rememberBaseAddrs acrossSessions) — The Debugger will remember address offsets that you have set for a program even if you exit and restart MULTI.

You can set address offsets by assigning built-in variables _DATA and _TEXT in the Debugger or by using the command line options -data offset and -text offset. For more information about system variables, see System Variables. For more information about command line options, see Command Line Reference.

Remember last connect command used for process

Permitted settings for this option are:

Selected (saveDebugServer on) — [default] Saves the most recently used Connection Method on a per-executable basis. If the executable is started and MULTI is not connected, the saved Connection Method will be used as the default in the Connection Chooser dialog box.
Cleared (saveDebugServer off) — The last Connection Method is not saved.

Automatically save changed connection files

Permitted settings for this option are:

Selected (autoSaveConnectionsinFiles on) — [default] MULTI saves any outstanding changes to all Target Connection files loaded in the Connection Organizer when you exit.
Cleared (autoSaveConnectionsinFiles off) — Changes to Target Connection files will not be automatically saved.

Automatically save 'User Methods' changes

Permitted settings for this option are:

Selected (autoSaveUserConnections on) — [default] MULTI saves any outstanding changes to the “User Methods” Target Connection file when you exit.
Cleared (autoSaveUserConnections off) — All changes to the “User Methods” Target Connection file will be lost, even if Automatically save changed connection files is selected (autoSaveConnectionsInFiles on).

Directory memory

Determine which directory to initially display in the File Chooser. Permitted settings for this option are:

Across Sessions (rememberDirs rememberAcross) — File Chooser will always open in the previously viewed directory for the same operation, even after closing and restarting MULTI. The user directories will only be used on the very first run of MULTI, or if a user settings file cannot be found.
Within Sessions (rememberDirs rememberWithin) — [default] File Chooser will open in the appropriate previously viewed directory, but it will not remember directories viewed in previous sessions. File Chooser will use the User directories initially each time MULTI is restarted.
None (rememberDirs rememberNever) — File Chooser will always open with the appropriate User directory, and never remember which directory was previously viewed.

User Directories

Opens the User Directories dialog box, which sets the directories the file chooser starts with if directory memory is not available or is turned off.

To change any of the settings in this dialog box, select the check box, then enter the full path of the directory.

General Files:

Selected (genFileSet on) — Opens the General Files directory field, where you can enter the path.
Cleared (genFileSet off) — [default] The current working directory is used.
General Files directory (genFilesDir pathname) — [default is current working directory] Use this field to enter the directory path for general files.

Source Files:

Selected (sourceFileSet on) — Opens the Source Files directory field, where you can enter the path.
Cleared (sourceFileSet off) — [default] The current working directory is used.
Source Files directory (sourceFilesDir pathname) — [default is current working directory] Use this field to enter the directory path for source files.

Project Files:

Selected (buildFileSet on) — Opens the Project Files directory field, where you can enter the path.
Cleared (buildFileSet off) — [default] The current working directory is used.
Project Files directory (buildFilesDir pathname) — [default is current working directory] Use this field to enter the directory path for project files.

Executables/Binaries:

Selected (execFileSet on) — Opens the Executables/Binaries directory field, where you can enter the path.
Cleared (execFileSet off) — [default] The current working directory is used.
Executables/Binaries directory (execFilesDir pathname) — [default is current working directory] Use this field to enter the directory path for executables.

Debug Servers:

Selected (debugServerSet on) — Opens the Debug Servers directory field, where you can enter the path.
Cleared (debugServerSet off) — [default] The current working directory is used.
Debug Servers directory (debugServersDir pathname) — [default is current working directory] Use this field to enter the directory path for debug servers.

Load Color Scheme

Linux/Solaris only

Sets the color scheme. Permitted settings for this option are:

Default (color, white background)
Beige (color, light background)
Plum (color, light background)
Dark 1 (color, black background)
Dark 2 (color, black background)
Grey (grey, white background)
Dark Grey (greys, black background)

Global Colors

Linux/Solaris only

Global colors can only be set on Linux/Solaris systems. They affect the default colors for user interface elements. The following global color options may be set:

Background (background color) — [default is #ffffff] Background color of user areas, such as the color behind the text you enter.
Foreground (foreground color) — [default is #000000] Color of text.
Control Area (controlColor color) — [default is #c0c0c0] Background color of control areas, such as menu bars and buttons.
Selection (Select color) — [default is #000080] Background color of text selections. The foreground color of selections is based on the foreground setting and is chosen automatically.

Debugger Colors*

Controls how certain elements are displayed in the Debugger. The colors you can customize are:

Assembly (assembly color) — [default is #0000ff] Color of interlaced assembly code.
Break Dot (bDotColor color) — [default is #00cd00] Color of breakdots, which indicate locations where breakpoints may be set.
Status (breakColor color) — [default is #ff0000] Color of the process status and debug server messages (STOPPED,RUNNING, etc.).
Context Arrow (pointerColor color) — [default is #0000ff] Color of the context arrow, which indicates what context to use for commands in the Debugger.
File line #
- Selected (useFileRelLineBg on) — [default] Enables file relative line numbers.
- Cleared (useFileRelLineBg off) — Disables file relative line numbers.
- Color field (fileRelLineBg color) — [default is #FFFFFF] Color of the background behind the column of file relative line numbers in the source pane.
Func line #
- Selected (useProcRelLineBg on) — [default ] Enables function relative line numbers.
- Cleared (useProcRelLineBg off) — Disables function relative line numbers.
- Color field (ProcRelLineBg color) — [default is #e4e4e4] Color of the background behind the column of function relative line numbers in the source pane.

Syntax Coloring

Permitted settings for this option are:

Selected (colorSyntax on) — [default] Source code will be syntax colored based upon the Syntax Color Settings listed below.
Cleared (colorSyntax off) — Source code will not be syntax colored.

If you change the setting of this option but do not save the configuration as the default, only the MULTI tool from which the option was changed is aware of the new setting. If you do save the configuration as the default, however, all MULTI tools launched after the change are also notified of the new setting.

Syntax Color Settings*

Colors may be set for the following items:

Comments (comment color) — [default is #008000]
Keywords (keyword color) — [default is #0000ff]
Dead Code (deadCode color) — [default is #808080] Color of code enclosed in an #if 0 ... #endif block.
Numbers (number color) — [default is #e000e0]
Strings (string color) — [default is #800000]
Characters (character color) — [default is #c000c0]
Customized (customized color) — [default is #008080]

Color C++ comments in C

Permitted settings for this option are:

Selected (cppCommentsinC on) — [default] C++ style comments (//) will be syntax colored as comments in both C++ and C source files.
Cleared (cppCommentsinC off) — C++ style comments will not be syntax colored as comments in C source files.

More Color Options

Opens the More Color Options dialog box, which contains additional colors that you can configure. For more information, see "The More Color Options Dialog Box" in the MULTI: Building Applications book for your target.

Connection Organizer Colors

Sets the foreground color of the Connected Targets list, which is located in the Connection Organizer.

Connected targets (startedConnectionFg color) — [default is #008000]

Diffview Colors

Sets the background color of the current selection in the Diff Viewer foreground.

Highlight (diffHighlight color) — [default is #e0ffd0]