Options

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

–aix_use_fast_trap

Tells MemoryScape that it support the AIX fast trap mechanism. You must either set this option on the command line or place it within a .memrc file.

–bg color

Same as –background.

–compiler_vars

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.

–no_compiler_vars

(Default) Tells MemoryScape that it should not show variables created by the Fortran compiler.

–control_c_quick_shutdown
–ccq

(Default) Tells MemoryScape to kill attached processes and exit.

–no_control_c_quick_shutdown
–nccq

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.

–debug_file consoleoutputfile

Redirects MemoryScape console output to a file named consoleoutputfile.

Default:

All MemoryScape console output is written to stderr.

–display displayname

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

Default:

The value of your DISPLAY environment variable.

–dump_core

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

–no_dumpcore

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

–env variable=value

Tells MemoryScape to add an environment variable to the environment variables passed to your program by the shell. If the variable already exists, it effectively 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.

–nptl_threads

Tells MemoryScape that your application is using NPTL threads. You only need to use this option if MemoryScape cannot determine that which thread package your program is using.

–no_nptl_threads

Tells MemoryScape that you are not using the NPTL threads package. Use this option if MemoryScape thinks your application is using it and it isn’t.

–pid pid

Tells MemoryScape to attach to process pid after it starts executing.

–search_path pathlist

Specifies a colon-separated list of directories that MemoryScape will search when it looks for source files. For example:

memscape –search_path proj/bin:proj/util

–signal_handling_mode “action_list”

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:

“Resend=SIGTERM”

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:

“Stop=* Error=SIGSEGV,SIGBUS \

Resend=SIGHUP”

–shm “action_list”

Same as –signal_handling_mode.

–stderr pathname

Names the file to which your program will write stderr information while executing within MemoryScape. If the file exists, MemoryScape overwrites it.

–stderr_append

Tells MemoryScape to append the information it writes to stderr to the file named in the –stderr command or the file named in GUI or a MemoryScape variable. If the file does not exist, MemoryScape creates it.

–stderr_is_stdout pathname

Tells MemoryScape to redirect stderr to stdout.

–stdin pathname

Names the file from which your program will read information while executing within MemoryScape.

–stdout pathname

Names the file to which your program will write stdout information while executing within MemoryScape. If the file exists, MemoryScape overwrites it.

–stdout_append

Tells MemoryScape to append the information it writes to stdout to the file named in the –stdout option or the file named in a MemoryScape variable. If the file does not exist, MemoryScape creates it.

–verbosity level

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

Default:

info