(Config > Options... > Debugger > More Debugger Options...)
To have MULTI automatically follow pointers when it encounters them instead of just printing the pointer value, enable this option. When on, MULTI shows the value of the pointer and what it points to. Disabled, MULTI only shows the value of the pointer.
Ensure that the commands being associated with a breakpoint pass syntax checking when the breakpoint is set. With this option on, breakpoints whose commands fail syntax checking cannot be set. Disabled, a syntax error in a breakpoint command will not be detected by MULTI until the breakpoint is hit and MULTI tries to execute the breakpoint's commands.
Format: continueplaybackfileonerror
Ignore errors in script files (.rc files). Disabled, the Debugger will stop running a script file if an error is encountered.
Ensure that no Debugger commands execute until a step or next finishes. Disabled, scripts that use s or n can appear to behave inconsistently since subsequent commands can appear to be lost sometimes, when in reality they just happened before the step or next finished. A step or next can be made 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.
Print the location of a variable (address in memory or register name) before printing the value of the variable when using the print command.
Display the typedef'ed name of a type instead of the actual (self-contained) type.
Format: showposinnodisplaymode
Print the current line after every command in non-GUI mode.
Format: disablecarriagereturnrepeat
The meaning of this command varies according to whether you access it through the Config Menu, or through the command line or a config file.
To make the return key repeat the last entered command when running in non-GUI mode, turn this option on in the GUI.
If setting this option from the command line or a config file, turn this option on to disable repetition of the last command via the return key.
When nexting over a subroutine that calls longjmp or does a C++ exception throw (a call to longjmp internally), the subroutine never returns in the normal way. This is significant because the debugger uses a temporary breakpoint just after the normal return to effect the next (this is also true of step if there is no source available for the subroutine). When longjmp is called, this temporary breakpoint is bypassed, and execution can "run away" instead of just nexting.
This configuration option controls how MULTI handles this situation.
Ignore/RunAway (IgnoreRunAway) - Let the code call longjmp without worrying about the consequences to a next.
Minimize Temp Stops (MinimizeTempStops) - Fix the problem in a way that doesn't cause temporary stops in longjmp as the program runs normally under the debugger. This option inserts and removes a temporary breakpoint for each next over a subroutine.
Maximize Step Speed (MaximizeStepSpeed) - Fix the problem in a way that minimizes the time it takes to do a next. This option leaves a breakpoint in longjmp, and will result in a temporary stop if longjmp is called when the program is running normally under the debugger.
Maximum number of bytes of memory used for the command pane scroll-back buffer. Increase this value if you keep scrolling back only to find that the thing you are interested in has scrolled out of the top of the buffer.
Number of seconds to wait for the debug server before assuming it is dead and disconnecting from it. A number that is too low will sometimes mistakenly disconnect from the debug server, and is not recommended. A fairly high number can be useful for very slow debug servers or debug servers that are being debugged. A high number can be frustrating if the debug server actually does die from time to time, because it keeps the debugger from accepting input while it's waiting to time out.