3 .\" (C) 2003 Ximian, Inc.
4 .\" (C) 2004-2005 Novell, Inc.
6 .\" Miguel de Icaza (miguel@gnu.org)
8 .de Sp \" Vertical space (when we can't use .PP)
14 mono \- Mono's ECMA-CLI native code generator (Just-in-Time and Ahead-of-Time)
17 .B mono [options] file [arguments...]
19 \fImono\fP is a runtime implementation of the ECMA Common Language
20 Infrastructure. This can be used to run ECMA and .NET applications.
22 The runtime contains a native code generator that transforms the
23 Common Intermediate Language into native code.
25 The code generator can operate in two modes: just in time compilation
26 (JIT) or ahead of time compilation (AOT). Since code can be
27 dynamically loaded, the runtime environment and the JIT are always
28 present, even if code is compiled ahead of time.
30 The runtime loads ths specified
37 is an ECMA assembly. They typically have a .exe or .dll extension.
39 The runtime provides a number of configuration options for running
40 applications, for developping and debugging, and for testing and
41 debugging the runtime itself.
43 The following options are available:
46 This option is used to precompile the CIL code in the specified
47 assembly to native code. The generated code is stored in a file with
48 the extension .so. This file will be automatically picked up by the
49 runtime when the assembly is executed.
51 Ahead-of-Time compilation is most useful if you use it in combination
52 with the -O=all,-shared flag which enables all of the optimizations in
53 the code generator to be performed. Some of those optimizations are
54 not practical for Just-in-Time compilation since they might be very
57 Unlike the .NET Framework, Ahead-of-Time compilation will not generate
58 domain independent code: it generates the same code that the
59 Just-in-Time compiler would produce. Since most applications use a
60 single domain, this is fine. If you want to optimize the generated
61 code for use in multi-domain applications, consider using the
64 This pre-compiles the methods, but the original assembly is still
65 required to execute as this one contains the metadata and exception
66 information which is not availble on the generated file. When
67 precompiling code, you might want to compile with all optimizations
68 (-O=all). Pre-compiled code is position independent code.
70 Pre compilation is just a mechanism to reduce startup time, and avoid
71 just-in-time compilation costs. The original assembly must still be
72 present, as the metadata is contained there.
74 .I "--config filename"
75 Load the specified configuration file instead of the default one(s).
76 The default files are /etc/mono/config and ~/.mono/config or the file
77 specified in the MONO_CONFIG environment variable, if set. See the
78 mono-config(5) man page for details on the format of this file.
81 Configures the virtual machine to be better suited for desktop
82 applications. Currently this sets the GC system to avoid expanding
83 the heap as much as possible at the expense of slowing down garbage
87 Displays usage instructions.
89 .I "--optimize=MODE", "-O=mode"
90 MODE is a comma separated list of optimizations. They also allow
91 optimizations to be turned off by prefixing the optimization name with
94 The following optimizations are implemented:
96 all Turn on all optimizations
97 peephole Peephole postpass
98 branch Branch optimizations
99 inline Inline method calls
100 cfold Constant folding
101 consprop Constant propagation
102 copyprop Copy propagation
103 deadce Dead code elimination
104 linears Linear scan global reg allocation
105 cmov Conditional moves
106 shared Emit per-domain code
107 sched Instruction scheduling
108 intrins Intrinsic method implementations
109 tailc Tail recursion and tail calls
110 loop Loop related optimizations
111 fcmov Fast x86 FP compares
112 leaf Leaf procedures optimizations
113 aot Usage of Ahead Of Time compiled code
114 precomp Precompile all methods before executing Main
115 abcrem Array bound checks removal
116 ssapre SSA based Partial Redundancy Elimination
119 For example, to enable all the optimization but dead code
120 elimination and inlining, you can use:
122 -O=all,-deadce,-inline
126 Activate the security manager (experimental feature in 1.1). This allows
127 mono to support declarative security attributes (e.g. execution of, CAS
128 or non-CAS, security demands). The security manager is OFF by default
132 Configures the virtual machine to be better suited for server
136 Prints JIT version information.
139 .SH DEVELOPMENT OPTIONS
140 The following options are used to help when developing a JITed application.
143 Turns on the debugging mode in the runtime. If an assembly was
144 compiled with debugging information, it will produce line number
145 information for stack traces.
147 .I "--profile[=profiler[:profiler_args]]"
148 Turns on profiling. For more information about profiling applications
149 and code coverage see the sections "PROFILING" and "CODE COVERAGE"
152 .I "--trace[=expression]"
153 Shows method names as they are invoked. By default all methods are
156 The trace can be customized to include or exclude methods, classes or
157 assemblies. A trace expression is a comma separated list of targets,
158 each target can be prefixed with a minus sign to turn off a particular
159 target. The words `program' and `all' have special meaning.
160 `program' refers to the main program being executed, and `all' means
161 all the method calls.
163 Assemblies are specified by their name, for example, to trace all
164 calls in the System assembly, use:
167 mono --trace=System app.exe
170 Classes are specified with the T: prefix. For example, to trace all
171 calls to the System.String class, use:
174 mono --trace=T:System.String app.exe
177 And individual methods are referenced with the M: prefix, and the
178 standar method notation:
181 mono --trace=M:System.Console:WriteLine app.exe
184 As previously noted, various rules can be specified at once:
187 mono --trace=T:System.String,T:System.Random app.exe
190 You can exclude pieces, the next example traces calls to
191 System.String except for the System.String:Concat method.
194 mono --trace=T:System.String,-M:System.String:Concat
197 Finally, namespaces can be specified using the N: prefix:
200 mono --trace=N:System.Xml
203 .SH JIT MAINTAINER OPTIONS
204 The maintainer options are only used by those developing the runtime
205 itself, and not typically of interest to runtime users or developers.
208 Inserts a breakpoint before the method whose name is `method'
209 (namespace.class:methodname). Use `Main' as method name to insert a
210 breakpoint on the application's main method.
213 Inserts a breakpoint on exceptions. This allows you to debug your
214 application with a native debugger when an exception is thrown.
217 This compiles a method (namespace.name:methodname), this is used for
218 testing the compiler performance or to examine the output of the code
222 Compiles all the methods in an assembly. This is used to test the
223 compiler performance or to examine the output of the code generator
225 .I "--graph=TYPE METHOD"
226 This generates a postscript file with a graph with the details about
227 the specified method (namespace.name:methodname). This requires `dot'
228 and ghostview to be installed (it expects Ghostview to be called
231 The following graphs are available:
233 cfg Control Flow Graph (CFG)
235 code CFG showing code
236 ssa CFG showing code after SSA translation
237 optcode CFG showing code after IR optimizations
240 Some graphs will only be available if certain optimizations are turned
244 Instruct the runtime on the number of times that the method specified
245 by --compile (or all the methods if --compileall is used) to be
246 compiled. This is used for testing the code generator performance.
249 Displays information about the work done by the runtime during the
250 execution of an application.
252 .I "--wapi=hps|semdel"
253 Perform maintenance of the process shared data.
255 semdel will delete the global semaphore.
257 hps will list the currently used handles.
260 Increases the verbosity level, each time it is listed, increases the
261 verbosity level to include more information (including, for example,
262 a disassembly of the native code produced, code selector info etc.).
264 The mono runtime includes a profiler that can be used to explore
265 various performance related problems in your application. The
266 profiler is activated by passing the --profile command line argument
267 to the Mono runtime, the format is:
270 --profile[=profiler[:profiler_args]]
273 Mono has a built-in profiler called 'default' (and is also the default
274 if no arguments are specified), but developers can write custom
275 profilers, see the section "CUSTOM PROFILERS" for more details.
279 is not specified, the default profiler is used.
283 is a profiler-specific string of options for the profiler itself.
285 The default profiler accepts the following options 'alloc' to profile
286 memory consumption by the application; 'time' to profile the time
287 spent on each routine; 'jit' to collect time spent JIT-compiling methods
288 and 'stat' to perform sample statistical profiling.
289 If no options are provided the default is 'alloc,time,jit'.
292 profile data is printed to stdout: to change this, use the 'file=filename'
293 option to output the data to filename.
298 mono --profile program.exe
302 That will run the program with the default profiler and will do time
303 and allocation profiling.
307 mono --profile=default:stat,alloc,file=prof.out program.exe
310 Will do sample statistical profiling and allocation profiling on
311 program.exe. The profile data is put in prof.out.
313 Note that the statistical profiler has a very low overhead and should
314 be the preferred profiler to use (for better output use the full path
315 to the mono binary when running and make sure you have installed the
316 addr2line utility that comes from the binutils package).
318 There are a number of external profilers that have been developed for
319 Mono, we will update this section to contain the profilers.
321 The Live Type profiler shows at every GC iteration all of the live
322 objects of a given type. To install you must download the profiler
325 svn co svn://svn.myrealbox.com/source/trunk/heap-prof
332 To use the profiler, execute:
334 mono --profile=desc-heap program.exe
337 The output of this profiler looks like this:
339 Checkpoint at 102 for heap-resize
340 System.MonoType : 708
341 System.Threading.Thread : 352
343 System.String[] : 104
344 Gnome.ModuleInfo : 112
345 System.Object[] : 160
346 System.Collections.Hashtable : 96
348 System.Collections.Hashtable+Slot[] : 296
349 System.Globalization.CultureInfo : 108
350 System.Globalization.NumberFormatInfo : 144
353 The first line describes the iteration number for the GC, in this case
356 Then on each line the type is displayed as well as the number of bytes
357 that are being consumed by live instances of this object.
359 Mono provides a mechanism for loading other profiling modules which in
360 the form of shared libraries. These profiling modules can hook up to
361 various parts of the Mono runtime to gather information about the code
364 To use a third party profiler you must pass the name of the profiler
368 mono --profile=custom program.exe
372 In the above sample Mono will load the user defined profiler from the
373 shared library `mono-profiler-custom.so'. This profiler module must
374 be on your dynamic linker library path.
376 A list of other third party profilers is available from Mono's web
377 site (www.mono-project.com/Performance_Tips)
379 Custom profiles are written as shared libraries. The shared library
380 must be called `mono-profiler-NAME.so' where `NAME' is the name of
383 For a sample of how to write your own custom profiler look in the
384 Mono source tree for in the samples/profiler.c.
386 Mono ships with a code coverage module. This module is activated by
387 using the Mono --profile=cov option. The format is:
388 .I "--profile=cov[:assembly-name[/namespace]] test-suite.exe"
390 By default code coverage will default to all the assemblies loaded,
391 you can limit this by specifying the assembly name, for example to
392 perform code coverage in the routines of your program use, for example
393 the following command line limits the code coverage to routines in the
397 mono --profile=cov:demo demo.exe
403 does not include the extension.
405 You can further restrict the code coverage output by specifying a
409 mono --profile=cov:demo/My.Utilities demo.exe
413 Which will only perform code coverage in the given assembly and
416 Typical output looks like this:
419 Not covered: Class:.ctor ()
420 Not covered: Class:A ()
421 Not covered: Driver:.ctor ()
422 Not covered: Driver:method ()
423 Partial coverage: Driver:Main ()
428 The offsets displayed are IL offsets.
430 It is possible to obtain a stack trace of all the active threads in
431 Mono by sending the QUIT signal to Mono, you can do this from the
432 command line, like this:
436 Where pid is the Process ID of the Mono process you want to examine.
437 The process will continue running afterwards.
439 You can use the MONO_LOG_LEVEL and MONO_LOG_MASK environment variables
440 to get verbose debugging output about the execution of your
441 application within Mono.
445 environment variable if set, the logging level is changed to the set
446 value. Possible values are "error", "critical", "warning", "message",
447 "info", "debug". The default value is "error". Messages with a logging
448 level greater then or equal to the log level will be printed to
451 Use "info" to track the dynamic loading of assemblies.
456 environment variable to limit the extent of the messages you get:
457 If set, the log mask is changed to the set value. Possible values are
458 "asm" (assembly loader), "type", "dll" (native library loader), "gc"
459 (garbage collector), "cfg" (config file loader), "aot" (precompiler) and "all".
460 The default value is "all". Changing the mask value allows you to display only
461 messages for a certain component. You can use multiple masks by comma
462 separating them. For example to see config file messages and assembly loader
463 messages set you mask to "asm,cfg".
465 The following is a common use to track down problems with P/Invoke:
468 $ MONO_LOG_LEVEL="debug" MONO_LOG_MASK="dll" mono glue.exe
473 Mono's XML serialization engine by default will use a reflection-based
474 approach to serialize which might be slow for continous processing
475 (web service applications). The serialization engine will determine
476 when a class must use a hand-tuned serializer based on a few
477 parameters and if needed it will produce a customized C# serializer
478 for your types at runtime. This customized serializer then gets
479 dynamically loaded into your application.
481 You can control this with the MONO_XMLSERIALIZER_THS environment
484 The possible values are
486 to disable the use of a C# customized
487 serializer, or an integer that is the minimum number of uses before
488 the runtime will produce a custom serializer (0 will produce a
489 custom serializer on the first access, 50 will produce a serializer on
490 the 50th use). Mono will fallback to an interpreted serializer if the
491 serializer generation somehow fails. This behavior can be disabled
492 by setting the option
494 (for example: MONO_XMLSERIALIZER_THS=0,nofallback).
495 .SH ENVIRONMENT VARIABLES
498 Turns off the garbage collection in Mono. This should be only used
499 for debugging purposes
502 If set, this variable will instruct Mono to ahead-of-time compile new
503 assemblies on demand and store the result into a cache in
507 If set, this variable overrides the default system configuration directory
508 ($PREFIX/etc). It's used to locate machine.config file.
511 If set, this variable overrides the default runtime configuration file
512 ($PREFIX/etc/mono/config). The --config command line options overrides the
513 environment variable.
516 If set, enables some features of the runtime useful for debugging.
517 This variable should contain a comma separated list of debugging options.
518 Currently, the following options are supported:
522 .I "collect-pagefault-stats"
523 Collects information about pagefaults. This is used internally to
524 track the number of page faults produced to load metadata. To display
525 this information you must use this option with "--stats" command line option.
528 Captures the interrupt signal (Control-C) and displays a stack trace
529 when pressed. Useful to find out where the program is executing at a
530 given point. This only displays the stack trace of a single thread.
533 This option will leak delegate trampolines that are no longer
534 referenced as to present the user with more information about a
535 delegate missuse. Basically a delegate instance might be created,
536 passed to unmanaged code, and no references kept in managed code,
537 which will garbage collect the code. With this option it is possible
538 to track down the source of the problems.
542 .I "MONO_DISABLE_AIO"
543 If set, tells mono NOT to attempt using native asynchronous I/O services. In
544 that case, a default select/poll implementation is used. Currently only epoll()
547 .I "MONO_DISABLE_MANAGED_COLLATION"
548 If this environment variable is `yes', the runtime uses unmanaged
549 collation (which actually means no culture-sensitive collation). It
550 internally disables managed collation functionality invoked via the
551 members of System.Globalization.CompareInfo class. Collation is
555 For platforms that do not otherwise have a way of obtaining random bytes
556 this can be set to the name of a file system socket on which an egd or
557 prngd daemon is listening.
559 .I "MONO_EXTERNAL_ENCODINGS"
560 If set, contains a colon-separated list of text encodings to try when
561 turning externally-generated text (e.g. command-line arguments or
562 filenames) into Unicode. The encoding names come from the list
563 provided by iconv, and the special case "default_locale" which refers
564 to the current locale's default encoding.
566 When reading externally-generated text strings UTF-8 is tried first,
567 and then this list is tried in order with the first successful
568 conversion ending the search. When writing external text (e.g. new
569 filenames or arguments to new processes) the first item in this list
570 is used, or UTF-8 if the environment variable is not set.
572 The problem with using MONO_EXTERNAL_ENCODINGS to process your
573 files is that it results in a problem: although its possible to get
574 the right file name it is not necessarily possible to open the file.
575 In general if you have problems with encodings in your filenames you
576 should use the "convmv" program.
579 Provides a prefix the runtime uses to look for Global Assembly Caches.
580 Directories are separated by the platform path separator (colons on
581 unix). MONO_GAC_PREFIX should point to the top directory of a prefixed
582 install. Or to the directory provided in the gacutil /gacdir command. Example:
583 .B /home/username/.mono:/usr/local/mono/
585 .I "MONO_LOCAL_EVENTLOG_PATH"
586 It is required to enable local file based System.Diagnostics.EventLog
587 implementation. This variable is used to indicate a local directory to
588 store event logs (thus it must be writable by the user who runs
589 the runtime). By default, a null implementation is used i.e. EventLog
592 .I "MONO_MANAGED_WATCHER"
593 If set to any value, System.IO.FileSystemWatcher will use the default
594 managed implementation (slow). If unset, mono will try to use FAM under
595 Unix systems and native API calls on Windows, falling back to the
596 managed implementation on error.
599 Provides a search path to the runtime where to look for library files.
600 Directories are separated by the platform path separator (colons on unix). Example:
601 .B /home/username/lib:/usr/local/mono/lib
604 Experimental RTC support in the statistical profiler: if the user has
605 the permission, more accurate statistics are gathered. The MONO_RTC
606 value must be restricted to what the linux rtc allows: power of two
607 from 64 to 8192 Hz. To enable higher frequencies like 4096 Hz, run as root:
610 echo 4096 > /proc/sys/dev/rtc/max-user-freq
617 MONO_RTC=4096 mono --profiler=default:stat program.exe
622 Disable inlining of thread local accesses. Try setting this if you get a segfault
623 early on in the execution of mono.
626 If set its the directory where the ".wapi" handle state is stored.
627 This is the directory where the Windows I/O Emulation layer stores its
628 shared state data (files, events, mutexes, pipes). By default Mono
629 will store the ".wapi" directory in the users's home directory.
631 .I "MONO_SHARED_HOSTNAME"
632 Uses the string value of this variable as a replacement for the host name when
633 creating file names in the ".wapi" directory. This helps if the host name of
634 your machine is likely to be changed when a mono application is running or if
635 you have a .wapi directory shared among several different computers.
637 Mono typically uses the hostname to create the files that are used to
638 share state across multiple Mono processes. This is done to support
639 home directories that might be shared over the network.
641 .I "MONO_STRICT_IO_EMULATION"
642 If set, extra checks are made during IO operations. Currently, this
643 includes only advisory locks around file writes.
646 The name of the theme to be used by Windows.Forms. Available themes today
647 include "clearlooks", "nice" and "win32".
649 The default is "win32".
651 .I "MONO_THREADS_PER_CPU"
652 The maximum number of threads in the general threadpool will be
653 20 + (MONO_THREADS_PER_CPU * number of CPUs). The default value for this
656 .I "MONO_XMLSERIALIZER_THS"
657 Controls the threshold for the XmlSerializer to produce a custom
658 serializer for a given class instead of using the Reflection-based
659 interpreter. The possible values are `no' to disable the use of a
660 custom serializer or a number to indicate when the XmlSerializer
661 should start serializing. The default value is 50, which means that
662 the a custom serializer will be produced on the 50th use.
663 .SH ENVIRONMENT VARIABLES FOR DEBUGGING
665 .I "MONO_ASPNET_NODELETE"
666 If set to any value, temporary source files generated by ASP.NET support
667 classes will not be removed. They will be kept in the user's temporary
671 The logging level, possible values are `error', `critical', `warning',
672 `message', `info' and `debug'. See the DEBUGGING section for more
676 Controls the domain of the Mono runtime that logging will apply to.
677 If set, the log mask is changed to the set value. Possible values are
678 "asm" (assembly loader), "type", "dll" (native library loader), "gc"
679 (garbage collector), "cfg" (config file loader), "aot" (precompiler) and "all".
680 The default value is "all". Changing the mask value allows you to display only
681 messages for a certain component. You can use multiple masks by comma
682 separating them. For example to see config file messages and assembly loader
683 messages set you mask to "asm,cfg".
686 Used for runtime tracing of method calls. The format of the comma separated
695 disabled Trace output off upon start.
698 You can toggle trace output on/off sending a SIGUSR2 signal to the program.
700 .I "MONO_TRACE_LISTENER"
701 If set, enables the System.Diagnostics.DefaultTraceListener, which will
702 print the output of the System.Diagnostics Trace and Debug classes.
703 It can be set to a filename, and to Console.Out or Console.Error to display
704 output to standard output or standard error, respectively. If it's set to
705 Console.Out or Console.Error you can append an optional prefix that will
706 be used when writing messages like this: Console.Error:MyProgramName.
707 See the System.Diagnostics.DefaultTraceListener documentation for more
710 .I "MONO_XEXCEPTIONS"
711 This throws an exception when a X11 error is encountered; by default a
712 message is displayed but execution continues
715 This is used in the System.Windows.Forms implementation when running
716 with the X11 backend. This is used to debug problems in Windows.Forms
717 as it forces all of the commands send to X11 server to be done
718 synchronously. The default mode of operation is asynchronous which
719 makes it hard to isolate the root of certain problems.
721 On Unix assemblies are loaded from the installation lib directory. If you set
722 `prefix' to /usr, the assemblies will be located in /usr/lib. On
723 Windows, the assemblies are loaded from the directory where mono and
728 The directory for the ahead-of-time compiler demand creation
729 assemblies are located.
731 /etc/mono/config, ~/.mono/config
733 Mono runtime configuration file. See the mono-config(5) manual page
734 for more information.
736 ~/.config/.mono/certs, /usr/share/.mono/certs
738 Contains Mono certificate stores for users / machine. See the certmgr(1)
739 manual page for more information on managing certificate stores and
740 the mozroots(1) page for information on how to import the Mozilla root
741 certificates into the Mono certificate store.
743 ~/.config/.mono/keypairs, /usr/share/.mono/keypairs
745 Contains Mono cryptographic keypairs for users / machine. They can be
746 accessed by using a CspParameters object with DSACryptoServiceProvider
747 and RSACryptoServiceProvider classes.
749 ~/.config/.isolatedstorage, ~/.local/share/.isolatedstorage, /usr/share/.isolatedstorage
751 Contains Mono isolated storage for non-roaming users, roaming users and
752 local machine. Isolated storage can be accessed using the classes from
753 the System.IO.IsolatedStorage namespace.
755 Mailing lists are listed at the
756 http://www.mono-project.com/Mailing_Lists
758 http://www.mono-project.com
760 .BR certmgr(1), mcs(1), mint(1), monodis(1), mono-config(5), mozroots(1).
762 For ASP.NET-related documentation, see the xsp(1) manual page
projects / mono.git / blob