Mono Command-line options
Contents
Execute
Dont forget the .exe!
mono <application.exe>
TODO: This is the printout of "man mono". It must be organized.
Options
--help , -h
Displays usage instructions.
--share-code
This mode makes the LoaderOptimization for Application Domains
default to sharing code. This results in slower code, but enables
code sharing across appli- cation domains. The default is to
maximize for speed, but disallow JITed code sharing across domains.
See System.LoaderOptimization for more information
--config filename
Load the specified configuration file instead of the default
one(s). The default files are /etc/mono/config and ~/.mono/config
or the file specified in the MONO_CONFIG environment variable, if
set.
--noinline
Disables the code inliner.
DEBUGGING OPTIONS
The following options are used to debug, or perfo- mance test the
JIT compiler:
--trace-calls
Shows method names as they are invoked.
--dump-asm
Displays the generated code as methods are invoked.
--dump-forest
Displays the basic blocks and the forest of trees that is created
from a stream of CIL opcodes.
--compile name
Compiles the method on the given class (names-
pace.name:methodname) or all classes in the given image
(@imagename).
--ncompile
Compiles the method a number of times. If no argu- ment is
specified, the method will be compiled a thousand times.
DEVELOPMENT OPTIONS
The following options are used to debug a JITed applica- tion.
They're only useful when running the JIT in a debugger:
--debug
Writes out debug information in the given format or in the default
format. See DEBUGGING FORMATS for details.
--debug-args args
Comma-separated list of additional arguments for the symbol writer.
See DEBUGGING FORMATS for details.
--break method
Inserts a breakpoint before the method whose name is `method'
(namespace.class:methodname). Use `Main' as method name to insert a
breakpoint on the application's main method.
--precompile name
Compiles the given class (namespace.name), method
(namespace.name:methodname) or all classes in the given image
(@imagename) before executing the main application.
--profile
Collect profiling information and dump it at the end of the
process.
DEBUGGING FORMATS
The following debugging formats are currently supported: stabs
Writes out stabs debug information. dwarf Writes out dwarf debug
information. mono Use a symbol file which has been created by MCS.
It can be used to get source lines in stack traces. The "stabs" and
"dwarf" formats support the following options:
filename=FILENAME
Write debugging information into FILENAME. This file must be run
through the assembler to create an object file.
objfile=FILENAME
When automatically assembling the symbol file, write the resulting
object file into FILENAME.
dont_assemble
Normally, the symbol file is automatically assem- bled to an object
file when you call "mono_debug_make_symbols". Use this option to
dis- able this behaviour.
install_il_files
Put the generated *.il files in the same directory than the
assembly they came from. The default is to put them into the
current working directory.
dont_update_il_files
Normally, the *.il files are recreated if their assemblies have
changed when you call "mono_debug_make_symbols". Use this option to
dis- able this behaviour.
dont_create_il_files
Update the *.il files if their assemblies have changed, but only if
the file already exists.
A. Credits
Author: Johannes Roith
(johannes@jroith.de)