Passes all subsequent arguments (specified by args) to the program specified by filename. This option must be the last on the command line.

Specifies use of the AIX fast trap mechanism. You must either set this option on the command line or place it within a .memrc file.

Same as -background.

Some Fortran compilers (HP f90/f77, HP f90, SGI 7.2 compilers) output debugging information that describes variables the compiler itself has invented for purposes such as passing the length of character*(*) variables. By default, MemoryScape suppresses the display of these compiler-generated variables.

However, you can specify the -compiler_vars option to display these variables. This is useful when you are looking for a corruption of a runtime descriptor or are writing a ­compiler.

(Default) Does not show variables created by the Fortran compiler.

(Default) Kills attached processes and exits.

Invokes code that sometimes allows MemoryScape to better manage the way it kills parallel jobs when it works with management systems. This has only been tested with SLURM. It may not work with other systems.

Redirects MemoryScape console output to a file named consoleoutputfile.

Sets the name of the X Windows display to displayname. For example, -display vinnie:0.0 displays MemoryScape on the machine named “vinnie.”

Dumps a MemoryScape core file when an internal error occurs. This is used to help Rogue Wave Software debug MemoryScape problems.

(Default) Does not dump a core file when it gets an internal error.

Adds an environment variable to the environment variables passed to your program by the shell. If the variable already exists, this option replaces the previous value. You need to use this command for each variable being added; that is, you cannot add more than one variable with an env command.

Specifies the use of NPTL threads by your application. You need to use this option only if MemoryScape cannot determine which thread package your program is using.

Specifies that your application is not using the NPTL threads package. Use this option only if MemoryScape thinks your application is using it when it is not.

Attaches to process pid after it starts executing.

Specifies a colon-separated list of directories to search for source files. For example:

memscape -search_path proj/bin:proj/util

Modifies the way in which MemoryScape handles signals. You must enclose the action_list string in quotation marks to protect it from the shell.

An action_list consists of a list of signal_action descriptions separated by spaces:

signal_action[ signal_action] ...

A signal action description consists of an action, an equal sign (=), and a list of signals:

action=signal_list

An action can be one of the following: Error, Stop, Resend, or Discard.

A signal_specifier can be a signal name (such as ­SIGSEGV), a signal number (such as 11), or a star (*), which specifies all signals. We recommend that you use the signal name rather than the number because number assignments vary across UNIX sessions.

The following rules apply when you are specifying an action_list:

(1) If you specify an action for a signal in an action_list, MemoryScape changes the default action for that ­signal.

(2) If you do not specify a signal in the action_list, MemoryScape does not change its default action for the signal.

(3) If you specify a signal that does not exist for the platform, MemoryScape ignores it.

(4) If you specify an action for a signal more than once, MemoryScape uses the last action specified.

If you need to revert the settings for signal handling to MemoryScape’s built-in defaults, use the Defaults button in the File > Signals dialog box.

For example, here’s how to set the default action for the SIGTERM signal to resend:

Here’s how to set the action for SIGSEGV and SIGBUS to error, the action for SIGHUP to resend, and all remaining signals to stop:

Same as -signal_handling_mode.

Names the file to which MemoryScape writes the target program’s stderr information while executing within MemoryScape. If the file exists, MemoryScape overwrites it. If the file does not exist, MemoryScape creates it.

Tells MemoryScape to append the target program’s stderr information to the file named in the -stderr command or specified in the GUI. If the file does not exist, MemoryScape creates it.

Redirects the target program’s stderr to stdout.

Names the file from which the target program reads information while executing within MemoryScape.

Names the file to which MemoryScape writes the target program’s stdout information while executing within MemoryScape. If the file exists, MemoryScape overwrites it. If the file does not exist, MemoryScape creates it.

Tells MemoryScape to append the target program’s stdout information to the file named in the -stdout command or specified in the GUI. If the file does not exist, MemoryScape creates it.

Sets the verbosity level of MemoryScape-generated messages to level, which can be one of silent, error, warning, or info.