3 .\" Copyright 2003 Ximian, Inc.
4 .\" Copyright 2004-2011 Novell, Inc.
5 .\" Copyright 2011-2012 Xamarin Inc
6 .\" Copyright 2013 7digital Media Ltd.
8 .\" Miguel de Icaza (miguel@gnu.org)
12 mono \- Mono's ECMA-CLI native code generator (Just-in-Time and Ahead-of-Time)
15 .B mono [options] file [arguments...]
17 .B mono-sgen [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 the 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 developing and debugging, and for testing and
41 debugging the runtime itself.
43 The \fImono\fP command uses the Boehm conservative garbage collector
44 while the \fImono-sgen\fP command uses a moving and generational
47 On Unix-based systems, Mono provides a mechanism to emulate the
48 Windows-style file access, this includes providing a case insensitive
49 view of the file system, directory separator mapping (from \\ to /) and
50 stripping the drive letters.
52 This functionality is enabled by setting the
54 environment variable to one of
59 See the description for
61 in the environment variables section for more details.
63 The following options are available:
65 \fB--aot\fR, \fB--aot[=options]\fR
66 This option is used to precompile the CIL code in the specified
67 assembly to native code. The generated code is stored in a file with
68 the extension .so. This file will be automatically picked up by the
69 runtime when the assembly is executed.
71 Ahead-of-Time compilation is most useful if you use it in combination
72 with the -O=all,-shared flag which enables all of the optimizations in
73 the code generator to be performed. Some of those optimizations are
74 not practical for Just-in-Time compilation since they might be very
77 Unlike the .NET Framework, Ahead-of-Time compilation will not generate
78 domain independent code: it generates the same code that the
79 Just-in-Time compiler would produce. Since most applications use a
80 single domain, this is fine. If you want to optimize the generated
81 code for use in multi-domain applications, consider using the
84 This pre-compiles the methods, but the original assembly is still
85 required to execute as this one contains the metadata and exception
86 information which is not available on the generated file. When
87 precompiling code, you might want to compile with all optimizations
88 (-O=all). Pre-compiled code is position independent code.
90 Pre compilation is just a mechanism to reduce startup time, increase
91 code sharing across multiple mono processes and avoid just-in-time
92 compilation program startup costs. The original assembly must still
93 be present, as the metadata is contained there.
95 AOT code typically can not be moved from one computer to another
96 (CPU-specific optimizations that are detected at runtime) so you
97 should not try to move the pre-generated assemblies or package the
98 pre-generated assemblies for deployment.
100 A few options are available as a parameter to the
102 command line option. The options are separated by commas, and more
103 than one can be specified:
108 The AOT compiler will emit a (ELF only) library initializer to automatically
109 register the aot compiled module with the runtime. This is only useful in static
113 Instructs the AOT compiler to output assembly code instead of an
116 .I bind-to-runtime-version
118 If specified, forces the generated AOT files to be bound to the
119 runtime version of the compiling Mono. This will prevent the AOT
120 files from being consumed by a different Mono runtime.
122 This is currently an experimental feature as it is not complete.
123 This instructs Mono to precompile code that has historically not been
124 precompiled with AOT.
128 When this option is specified, P/Invoke methods are invoked directly
129 instead of going through the operating system symbol lookup operation.
131 .I llvm-path=<PREFIX>
132 Same for the llvm tools 'opt' and 'llc'.
135 Use the GNU style target triple <TRIPLE> to determine some code generation options, i.e.
136 --mtriple=armv7-linux-gnueabi will generate code that targets ARMv7. This is currently
137 only supported by the ARM backend. In LLVM mode, this triple is passed on to the LLVM
140 .I nimt-trampolines=[number]
141 When compiling in full aot mode, the IMT trampolines must be precreated
142 in the AOT image. You can add additional method trampolines with this argument.
146 Instructs the AOT compiler to not output any debugging information.
149 Instructs the AOT compiler to emit DWARF debugging information. When
150 used together with the nodebug option, only DWARF debugging
151 information is emitted, but not the information that can be used at
154 .I nrgctx-trampolines=[number]
155 When compiling in full aot mode, the generic sharing trampolines must be precreated
156 in the AOT image. You can add additional method trampolines with this argument.
159 .I ntrampolines=[number]
160 When compiling in full aot mode, the method trampolines must be precreated
161 in the AOT image. You can add additional method trampolines with this argument.
164 .I outfile=[filename]
165 Instructs the AOT compiler to save the output to the specified file.
167 .I print-skipped-methods
168 If the AOT compiler cannot compile a method for any reason, enabling this flag
169 will output the skipped methods to the console.
171 .I readonly-value=namespace.typename.fieldname=type/value
172 Override the value of a static readonly field. Usually, during JIT
173 compilation, the static constructor is ran eagerly, so the value of
174 a static readonly field is known at compilation time and the compiler
175 can do a number of optimizations based on it. During AOT, instead, the static
176 constructor can't be ran, so this option can be used to set the value of such
177 a field and enable the same set of optimizations.
178 Type can be any of i1, i2, i4 for integers of the respective sizes (in bytes).
179 Note that signed/unsigned numbers do not matter here, just the storage size.
180 This option can be specified multiple times and it doesn't prevent the static
181 constructor for the type defining the field to execute with the usual rules
182 at runtime (hence possibly computing a different value for the field).
185 .I save-temps,keep-temps
186 Instructs the AOT compiler to keep temporary files.
189 This instructs the compiler to generate sequence point checks that
190 allow Mono's soft debugger to debug applications even on systems where
191 it is not possible to set breakpoints or to single step (certain
192 hardware configurations like the cell phones and video gaming
196 Create an ELF object file (.o) or .s file which can be statically linked into an
197 executable when embedding the mono runtime. When this option is used, the object file
198 needs to be registered with the embedded runtime using the mono_aot_register_module
199 function which takes as its argument the mono_aot_module_<ASSEMBLY NAME>_info global
200 symbol from the object file:
203 extern void *mono_aot_module_hello_info;
205 mono_aot_register_module (mono_aot_module_hello_info);
210 Print various stats collected during AOT compilation.
213 This is an experimental option for the AOT compiler to use multiple threads
214 when compiling the methods.
216 .I tool-prefix=<PREFIX>
217 Prepends <PREFIX> to the name of tools ran by the AOT compiler, i.e. 'as'/'ld'. For
218 example, --tool=prefix=arm-linux-gnueabi- will make the AOT compiler run
219 'arm-linux-gnueabi-as' instead of 'as'.
222 Instructs the AOT compiler to emit debug symbol information.
224 For more information about AOT, see: http://www.mono-project.com/AOT
227 \fB--attach=[options]\fR
228 Currently the only option supported by this command line argument is
229 \fBdisable\fR which disables the attach functionality.
231 \fB--config filename\fR
232 Load the specified configuration file instead of the default one(s).
233 The default files are /etc/mono/config and ~/.mono/config or the file
234 specified in the MONO_CONFIG environment variable, if set. See the
235 mono-config(5) man page for details on the format of this file.
237 \fB--debugger-agent=[options]\fR
238 This instructs the Mono runtime to
239 start a debugging agent inside the Mono runtime and connect it to a
240 client user interface will control the Mono process.
241 This option is typically used by IDEs, like the MonoDevelop IDE.
243 The configuration is specified using one of more of the following options:
249 Use this option to specify the IP address where your debugger client is
254 Specifies the diagnostics log level for
258 Used to specify the file where the log will be stored, it defaults to
262 Defaults to no, with the default option Mono will actively connect to the
263 host/port configured with the \fBaddress\fR option. If you set it to 'y', it
264 instructs the Mono runtime to start debugging in server mode, where Mono
265 actively waits for the debugger front end to connect to the Mono process.
266 Mono will print out to stdout the IP address and port where it is listening.
269 Defaults to yes, with the default option Mono will suspend the vm on startup
270 until it connects successfully to a debugger front end. If you set it to 'n', in
271 conjunction with \fBserver=y\fR, it instructs the Mono runtime to run as normal,
272 while caching metadata to send to the debugger front end on connection..
274 .I transport=transport_name
276 This is used to specify the transport that the debugger will use to
277 communicate. It must be specified and currently requires this to
283 Configures the virtual machine to be better suited for desktop
284 applications. Currently this sets the GC system to avoid expanding
285 the heap as much as possible at the expense of slowing down garbage
289 This is an experimental flag that instructs the Mono runtime to not
290 generate any code at runtime and depend exclusively on the code
291 generated from using mono --aot=full previously. This is useful for
292 platforms that do not permit dynamic code generation.
294 Notice that this feature will abort execution at runtime if a codepath
295 in your program, or Mono's class libraries attempts to generate code
296 dynamically. You should test your software upfront and make sure that
297 you do not use any dynamic features.
299 \fB--gc=boehm\fR, \fB--gc=sgen\fR
300 Selects the Garbage Collector engine for Mono to use, Boehm or SGen.
301 Currently this merely ensures that you are running either the
302 \fImono\fR or \fImono-sgen\fR commands. This flag can be set in the
303 \fBMONO_ENV_OPTIONS\fR environment variable to force all of your child
304 processes to use one particular kind of GC with the Mono runtime.
306 \fB--help\fR, \fB-h\fR
307 Displays usage instructions.
310 If the Mono runtime has been compiled with LLVM support (not available
311 in all configurations), Mono will use the LLVM optimization and code
312 generation engine to JIT or AOT compile.
314 For more information, consult: http://www.mono-project.com/Mono_LLVM
317 When using a Mono that has been compiled with LLVM support, it forces
318 Mono to fallback to its JIT engine and not use the LLVM backend.
320 \fB--optimize=MODE\fR, \fB-O=MODE\fR
321 MODE is a comma separated list of optimizations. They also allow
322 optimizations to be turned off by prefixing the optimization name with
325 In general, Mono has been tuned to use the default set of flags,
326 before using these flags for a deployment setting, you might want to
327 actually measure the benefits of using them.
329 The following optimizations are implemented:
331 all Turn on all optimizations
332 peephole Peephole postpass
333 branch Branch optimizations
334 inline Inline method calls
335 cfold Constant folding
336 consprop Constant propagation
337 copyprop Copy propagation
338 deadce Dead code elimination
339 linears Linear scan global reg allocation
340 cmov Conditional moves [arch-dependency]
341 shared Emit per-domain code
342 sched Instruction scheduling
343 intrins Intrinsic method implementations
344 tailc Tail recursion and tail calls
345 loop Loop related optimizations
346 fcmov Fast x86 FP compares [arch-dependency]
347 leaf Leaf procedures optimizations
348 aot Usage of Ahead Of Time compiled code
349 precomp Precompile all methods before executing Main
350 abcrem Array bound checks removal
351 ssapre SSA based Partial Redundancy Elimination
352 sse2 SSE2 instructions on x86 [arch-dependency]
353 gshared Enable generic code sharing.
356 For example, to enable all the optimization but dead code
357 elimination and inlining, you can use:
359 -O=all,-deadce,-inline
362 The flags that are flagged with [arch-dependency] indicate that the
363 given option if used in combination with Ahead of Time compilation
364 (--aot flag) would produce pre-compiled code that will depend on the
365 current CPU and might not be safely moved to another computer.
367 \fB--runtime=VERSION\fR
368 Mono supports different runtime versions. The version used depends on the program
369 that is being run or on its configuration file (named program.exe.config). This option
370 can be used to override such autodetection, by forcing a different runtime version
371 to be used. Note that this should only be used to select a later compatible runtime
372 version than the one the program was compiled against. A typical usage is for
373 running a 1.1 program on a 2.0 version:
375 mono --runtime=v2.0.50727 program.exe
378 \fB--security\fR, \fB--security=mode\fR
379 Activate the security manager, a currently experimental feature in
380 Mono and it is OFF by default. The new code verifier can be enabled
381 with this option as well.
385 Using security without parameters is equivalent as calling it with the
388 The following modes are supported:
391 This allows mono to support declarative security attributes,
392 e.g. execution of Code Access Security (CAS) or non-CAS demands.
395 Enables the core-clr security system, typically used for
396 Moonlight/Silverlight applications. It provides a much simpler
397 security system than CAS, see http://www.mono-project.com/Moonlight
398 for more details and links to the descriptions of this new system.
401 Enables the new verifier and performs basic verification for code
402 validity. In this mode, unsafe code and P/Invoke are allowed. This
403 mode provides a better safety guarantee but it is still possible
404 for managed code to crash Mono.
407 Enables the new verifier and performs full verification of the code
408 being executed. It only allows verifiable code to be executed.
409 Unsafe code is not allowed but P/Invoke is. This mode should
410 not allow managed code to crash mono. The verification is not as
411 strict as ECMA 335 standard in order to stay compatible with the MS
414 The security system acts on user code: code contained in mscorlib or
415 the global assembly cache is always trusted.
420 Configures the virtual machine to be better suited for server
421 operations (currently, allows a heavier threadpool initialization).
424 Verifies mscorlib and assemblies in the global
425 assembly cache for valid IL, and all user code for IL
428 This is different from \fB--security\fR's verifiable
429 or validil in that these options only check user code and skip
430 mscorlib and assemblies located on the global assembly cache.
432 \fB-V\fR, \fB--version\fR
433 Prints JIT version information (system configuration, release number
434 and branch names if available).
437 .SH DEVELOPMENT OPTIONS
438 The following options are used to help when developing a JITed application.
440 \fB--debug\fR, \fB--debug=OPTIONS\fR
441 Turns on the debugging mode in the runtime. If an assembly was
442 compiled with debugging information, it will produce line number
443 information for stack traces.
447 The optional OPTIONS argument is a comma separated list of debugging
448 options. These options are turned off by default since they generate
449 much larger and slower code at runtime.
451 The following options are supported:
454 Produces a detailed error when throwing a InvalidCastException. This
455 option needs to be enabled as this generates more verbose code at
459 Disable some JIT optimizations which are usually only disabled when
460 running inside the debugger. This can be helpful if you want to attach
461 to the running process with mdb.
464 Generate and register debugging information with gdb. This is only supported on some
465 platforms, and only when using gdb 7.0 or later.
469 \fB--profile[=profiler[:profiler_args]]\fR
470 Turns on profiling. For more information about profiling applications
471 and code coverage see the sections "PROFILING" and "CODE COVERAGE"
474 This option can be used multiple times, each time will load an
475 additional profiler. This allows developers to use modules that
476 extend the JIT through the Mono profiling interface.
478 \fB--trace[=expression]\fR
479 Shows method names as they are invoked. By default all methods are
482 The trace can be customized to include or exclude methods, classes or
483 assemblies. A trace expression is a comma separated list of targets,
484 each target can be prefixed with a minus sign to turn off a particular
485 target. The words `program', `all' and `disabled' have special
486 meaning. `program' refers to the main program being executed, and
487 `all' means all the method calls.
489 The `disabled' option is used to start up with tracing disabled. It
490 can be enabled at a later point in time in the program by sending the
491 SIGUSR2 signal to the runtime.
493 Assemblies are specified by their name, for example, to trace all
494 calls in the System assembly, use:
497 mono --trace=System app.exe
500 Classes are specified with the T: prefix. For example, to trace all
501 calls to the System.String class, use:
504 mono --trace=T:System.String app.exe
507 And individual methods are referenced with the M: prefix, and the
508 standard method notation:
511 mono --trace=M:System.Console:WriteLine app.exe
514 Exceptions can also be traced, it will cause a stack trace to be
515 printed every time an exception of the specified type is thrown.
516 The exception type can be specified with or without the namespace,
517 and to trace all exceptions, specify 'all' as the type name.
520 mono --trace=E:System.Exception app.exe
523 As previously noted, various rules can be specified at once:
526 mono --trace=T:System.String,T:System.Random app.exe
529 You can exclude pieces, the next example traces calls to
530 System.String except for the System.String:Concat method.
533 mono --trace=T:System.String,-M:System.String:Concat
536 You can trace managed to unmanaged transitions using
537 the wrapper qualifier:
540 mono --trace=wrapper app.exe
543 Finally, namespaces can be specified using the N: prefix:
546 mono --trace=N:System.Xml
550 \fB--no-x86-stack-align\fR
551 Don't align stack frames on the x86 architecture. By default, Mono
552 aligns stack frames to 16 bytes on x86, so that local floating point
553 and SIMD variables can be properly aligned. This option turns off the
554 alignment, which usually saves one intruction per call, but might
555 result in significantly lower floating point and SIMD performance.
558 Generate a JIT method map in a /tmp/perf-PID.map file. This file is then
559 used, for example, by the perf tool included in recent Linux kernels.
560 Each line in the file has:
563 HEXADDR HEXSIZE methodname
566 Currently this option is only supported on Linux.
567 .SH JIT MAINTAINER OPTIONS
568 The maintainer options are only used by those developing the runtime
569 itself, and not typically of interest to runtime users or developers.
572 Inserts a breakpoint before the method whose name is `method'
573 (namespace.class:methodname). Use `Main' as method name to insert a
574 breakpoint on the application's main method. You can use it also with
575 generics, for example "System.Collections.Generic.Queue`1:Peek"
578 Inserts a breakpoint on exceptions. This allows you to debug your
579 application with a native debugger when an exception is thrown.
582 This compiles a method (namespace.name:methodname), this is used for
583 testing the compiler performance or to examine the output of the code
587 Compiles all the methods in an assembly. This is used to test the
588 compiler performance or to examine the output of the code generator
590 \fB--graph=TYPE METHOD\fR
591 This generates a postscript file with a graph with the details about
592 the specified method (namespace.name:methodname). This requires `dot'
593 and ghostview to be installed (it expects Ghostview to be called
596 The following graphs are available:
598 cfg Control Flow Graph (CFG)
600 code CFG showing code
601 ssa CFG showing code after SSA translation
602 optcode CFG showing code after IR optimizations
605 Some graphs will only be available if certain optimizations are turned
609 Instruct the runtime on the number of times that the method specified
610 by --compile (or all the methods if --compileall is used) to be
611 compiled. This is used for testing the code generator performance.
614 Displays information about the work done by the runtime during the
615 execution of an application.
617 \fB--wapi=hps|semdel\fR
618 Perform maintenance of the process shared data.
620 semdel will delete the global semaphore.
622 hps will list the currently used handles.
624 \fB-v\fR, \fB--verbose\fR
625 Increases the verbosity level, each time it is listed, increases the
626 verbosity level to include more information (including, for example,
627 a disassembly of the native code produced, code selector info etc.).
629 The Mono runtime allows external processes to attach to a running
630 process and load assemblies into the running program. To attach to
631 the process, a special protocol is implemented in the Mono.Management
634 With this support it is possible to load assemblies that have an entry
635 point (they are created with -target:exe or -target:winexe) to be
636 loaded and executed in the Mono process.
638 The code is loaded into the root domain, and it starts execution on
639 the special runtime attach thread. The attached program should
640 create its own threads and return after invocation.
642 This support allows for example debugging applications by having the
643 csharp shell attach to running processes.
645 The mono runtime includes a profiler that can be used to explore
646 various performance related problems in your application. The
647 profiler is activated by passing the --profile command line argument
648 to the Mono runtime, the format is:
651 --profile[=profiler[:profiler_args]]
654 Mono has a built-in profiler called 'default' (and is also the default
655 if no arguments are specified), but developers can write custom
656 profilers, see the section "CUSTOM PROFILERS" for more details.
660 is not specified, the default profiler is used.
664 is a profiler-specific string of options for the profiler itself.
666 The default profiler accepts the following options 'alloc' to profile
667 memory consumption by the application; 'time' to profile the time
668 spent on each routine; 'jit' to collect time spent JIT-compiling methods
669 and 'stat' to perform sample statistical profiling.
670 If no options are provided the default is 'alloc,time,jit'.
673 profile data is printed to stdout: to change this, use the 'file=filename'
674 option to output the data to filename.
679 mono --profile program.exe
683 That will run the program with the default profiler and will do time
684 and allocation profiling.
688 mono --profile=default:stat,alloc,file=prof.out program.exe
691 Will do sample statistical profiling and allocation profiling on
692 program.exe. The profile data is put in prof.out.
694 Note that the statistical profiler has a very low overhead and should
695 be the preferred profiler to use (for better output use the full path
696 to the mono binary when running and make sure you have installed the
697 addr2line utility that comes from the binutils package).
699 This is the most advanced profiler.
701 The Mono \f[I]log\f[] profiler can be used to collect a lot of
702 information about a program running in the Mono runtime.
703 This data can be used (both while the process is running and later)
704 to do analyses of the program behaviour, determine resource usage,
705 performance issues or even look for particular execution patterns.
707 This is accomplished by logging the events provided by the Mono
708 runtime through the profiling interface and periodically writing
709 them to a file which can be later inspected with the mprof-report(1)
712 More information about how to use the log profiler is available on the
713 mprof-report(1) page.
715 Mono provides a mechanism for loading other profiling modules which in
716 the form of shared libraries. These profiling modules can hook up to
717 various parts of the Mono runtime to gather information about the code
720 To use a third party profiler you must pass the name of the profiler
724 mono --profile=custom program.exe
728 In the above sample Mono will load the user defined profiler from the
729 shared library `mono-profiler-custom.so'. This profiler module must
730 be on your dynamic linker library path.
732 A list of other third party profilers is available from Mono's web
733 site (www.mono-project.com/Performance_Tips)
735 Custom profiles are written as shared libraries. The shared library
736 must be called `mono-profiler-NAME.so' where `NAME' is the name of
739 For a sample of how to write your own custom profiler look in the
740 Mono source tree for in the samples/profiler.c.
742 Mono ships with a code coverage module. This module is activated by
743 using the Mono --profile=cov option. The format is:
744 \fB--profile=cov[:assembly-name[/namespace]] test-suite.exe\fR
746 By default code coverage will default to all the assemblies loaded,
747 you can limit this by specifying the assembly name, for example to
748 perform code coverage in the routines of your program use, for example
749 the following command line limits the code coverage to routines in the
753 mono --profile=cov:demo demo.exe
759 does not include the extension.
761 You can further restrict the code coverage output by specifying a
765 mono --profile=cov:demo/My.Utilities demo.exe
769 Which will only perform code coverage in the given assembly and
772 Typical output looks like this:
775 Not covered: Class:.ctor ()
776 Not covered: Class:A ()
777 Not covered: Driver:.ctor ()
778 Not covered: Driver:method ()
779 Partial coverage: Driver:Main ()
784 The offsets displayed are IL offsets.
786 A more powerful coverage tool is available in the module `monocov'.
787 See the monocov(1) man page for details.
789 To debug managed applications, you can use the
791 command, a command line debugger.
793 It is possible to obtain a stack trace of all the active threads in
794 Mono by sending the QUIT signal to Mono, you can do this from the
795 command line, like this:
801 Where pid is the Process ID of the Mono process you want to examine.
802 The process will continue running afterwards, but its state is not
806 this is a last-resort mechanism for debugging applications and should
807 not be used to monitor or probe a production application. The
808 integrity of the runtime after sending this signal is not guaranteed
809 and the application might crash or terminate at any given point
812 The \fB--debug=casts\fR option can be used to get more detailed
813 information for Invalid Cast operations, it will provide information
814 about the types involved.
816 You can use the MONO_LOG_LEVEL and MONO_LOG_MASK environment variables
817 to get verbose debugging output about the execution of your
818 application within Mono.
822 environment variable if set, the logging level is changed to the set
823 value. Possible values are "error", "critical", "warning", "message",
824 "info", "debug". The default value is "error". Messages with a logging
825 level greater then or equal to the log level will be printed to
828 Use "info" to track the dynamic loading of assemblies.
833 environment variable to limit the extent of the messages you get:
834 If set, the log mask is changed to the set value. Possible values are
835 "asm" (assembly loader), "type", "dll" (native library loader), "gc"
836 (garbage collector), "cfg" (config file loader), "aot" (precompiler),
837 "security" (e.g. Moonlight CoreCLR support) and "all".
838 The default value is "all". Changing the mask value allows you to display only
839 messages for a certain component. You can use multiple masks by comma
840 separating them. For example to see config file messages and assembly loader
841 messages set you mask to "asm,cfg".
843 The following is a common use to track down problems with P/Invoke:
846 $ MONO_LOG_LEVEL="debug" MONO_LOG_MASK="dll" mono glue.exe
851 Mono's XML serialization engine by default will use a reflection-based
852 approach to serialize which might be slow for continuous processing
853 (web service applications). The serialization engine will determine
854 when a class must use a hand-tuned serializer based on a few
855 parameters and if needed it will produce a customized C# serializer
856 for your types at runtime. This customized serializer then gets
857 dynamically loaded into your application.
859 You can control this with the MONO_XMLSERIALIZER_THS environment
862 The possible values are
864 to disable the use of a C# customized
865 serializer, or an integer that is the minimum number of uses before
866 the runtime will produce a custom serializer (0 will produce a
867 custom serializer on the first access, 50 will produce a serializer on
868 the 50th use). Mono will fallback to an interpreted serializer if the
869 serializer generation somehow fails. This behavior can be disabled
870 by setting the option
872 (for example: MONO_XMLSERIALIZER_THS=0,nofallback).
873 .SH ENVIRONMENT VARIABLES
876 Turns off the garbage collection in Mono. This should be only used
877 for debugging purposes
880 When Mono is compiled with LLVM support, this instructs the runtime to
881 stop using LLVM after the specified number of methods are JITed.
882 This is a tool used in diagnostics to help isolate problems in the
883 code generation backend. For example \fBLLVM_COUNT=10\fR would only
884 compile 10 methods with LLVM and then switch to the Mono JIT engine.
885 \fBLLVM_COUNT=0\fR would disable the LLVM engine altogether.
888 If set, this variable will instruct Mono to ahead-of-time compile new
889 assemblies on demand and store the result into a cache in
892 \fBMONO_ASPNET_INHIBIT_SETTINGSMAP\fR
893 Mono contains a feature which allows modifying settings in the .config files shipped
894 with Mono by using config section mappers. The mappers and the mapping rules are
895 defined in the $prefix/etc/mono/2.0/settings.map file and, optionally, in the
896 settings.map file found in the top-level directory of your ASP.NET application.
897 Both files are read by System.Web on application startup, if they are found at the
898 above locations. If you don't want the mapping to be performed you can set this
899 variable in your environment before starting the application and no action will
902 \fBMONO_ASPNET_WEBCONFIG_CACHESIZE\fR
903 Mono has a cache of ConfigSection objects for speeding up WebConfigurationManager
904 queries. Its default size is 100 items, and when more items are needed, cache
905 evictions start happening. If evictions are too frequent this could impose
906 unnecessary overhead, which could be avoided by using this environment variable
907 to set up a higher cache size (or to lower memory requirements by decreasing it).
909 \fBMONO_CAIRO_DEBUG_DISPOSE\fR
910 If set, causes Mono.Cairo to collect stack traces when objects are allocated,
911 so that the finalization/Dispose warnings include information about the
915 If set, this variable overrides the default system configuration directory
916 ($PREFIX/etc). It's used to locate machine.config file.
919 Sets the style of COM interop. If the value of this variable is "MS"
920 Mono will use string marhsalling routines from the liboleaut32 for the
921 BSTR type library, any other values will use the mono-builtin BSTR
925 If set, this variable overrides the default runtime configuration file
926 ($PREFIX/etc/mono/config). The --config command line options overrides the
927 environment variable.
930 Override the automatic cpu detection mechanism. Currently used only on arm.
931 The format of the value is as follows:
937 where V is the architecture number 4, 5, 6, 7 and the options can be currently be
941 MONO_CPU_ARCH="armv4 thumb" mono ...
945 \fBMONO_DISABLE_AIO\fR
946 If set, tells mono NOT to attempt using native asynchronous I/O services. In
947 that case, a default select/poll implementation is used. Currently only epoll()
950 \fBMONO_DISABLE_MANAGED_COLLATION\fR
951 If this environment variable is `yes', the runtime uses unmanaged
952 collation (which actually means no culture-sensitive collation). It
953 internally disables managed collation functionality invoked via the
954 members of System.Globalization.CompareInfo class. Collation is
957 \fBMONO_DISABLE_SHM\fR
958 Unix only: If set, disables the shared memory files used for
959 cross-process handles: process have only private handles. This means
960 that process and thread handles are not available to other processes,
961 and named mutexes, named events and named semaphores are not visible
964 This is can also be enabled by default by passing the
965 "--disable-shared-handles" option to configure.
967 This is the default from mono 2.8 onwards.
969 \fBMONO_DISABLE_SHARED_AREA\fR
970 Unix only: If set, disable usage of shared memory for exposing
971 performance counters. This means it will not be possible to both
972 externally read performance counters from this processes or read
973 those of external processes.
976 When set, enables the use of a fully managed DNS resolver instead of the
977 regular libc functions. This resolver performs much better when multiple
978 queries are run in parallel.
980 Note that /etc/nsswitch.conf will be ignored.
982 \fBMONO_EGD_SOCKET\fR
983 For platforms that do not otherwise have a way of obtaining random bytes
984 this can be set to the name of a file system socket on which an egd or
985 prngd daemon is listening.
987 \fBMONO_ENABLE_SHM\fR
988 Unix only: Enable support for cross-process handles. Cross-process
989 handles are used to expose process handles, thread handles, named
990 mutexes, named events and named semaphores across Unix processes.
992 \fBMONO_ENV_OPTIONS\fR
993 This environment variable allows you to pass command line arguments to
994 a Mono process through the environment. This is useful for example
995 to force all of your Mono processes to use LLVM or SGEN without having
996 to modify any launch scripts.
998 \fBMONO_ENV_OPTIONS\fR
999 Used to pass extra options to the debugger agent in the runtime, as they were passed
1000 using --debugger-agent=.
1002 \fBMONO_EVENTLOG_TYPE\fR
1003 Sets the type of event log provider to use (for System.Diagnostics.EventLog).
1005 Possible values are:
1010 Persists event logs and entries to the local file system.
1012 The directory in which to persist the event logs, event sources and entries
1013 can be specified as part of the value.
1015 If the path is not explicitly set, it defaults to "/var/lib/mono/eventlog"
1016 on unix and "%APPDATA%\mono\eventlog" on Windows.
1021 Uses the native win32 API to write events and registers event logs and
1022 event sources in the registry. This is only available on Windows.
1024 On Unix, the directory permission for individual event log and event source
1025 directories is set to 777 (with +t bit) allowing everyone to read and write
1026 event log entries while only allowing entries to be deleted by the user(s)
1031 Silently discards any events.
1034 The default is "null" on Unix (and versions of Windows before NT), and
1035 "win32" on Windows NT (and higher).
1038 \fBMONO_EXTERNAL_ENCODINGS\fR
1039 If set, contains a colon-separated list of text encodings to try when
1040 turning externally-generated text (e.g. command-line arguments or
1041 filenames) into Unicode. The encoding names come from the list
1042 provided by iconv, and the special case "default_locale" which refers
1043 to the current locale's default encoding.
1045 When reading externally-generated text strings UTF-8 is tried first,
1046 and then this list is tried in order with the first successful
1047 conversion ending the search. When writing external text (e.g. new
1048 filenames or arguments to new processes) the first item in this list
1049 is used, or UTF-8 if the environment variable is not set.
1051 The problem with using MONO_EXTERNAL_ENCODINGS to process your
1052 files is that it results in a problem: although its possible to get
1053 the right file name it is not necessarily possible to open the file.
1054 In general if you have problems with encodings in your filenames you
1055 should use the "convmv" program.
1057 \fBMONO_GC_PARAMS\fR
1058 When using Mono with the SGen garbage collector this variable controls
1059 several parameters of the collector. The variable's value is a comma
1060 separated list of words.
1064 \fBnursery-size=\fIsize\fR
1065 Sets the size of the nursery. The size is specified in bytes and must
1066 be a power of two. The suffixes `k', `m' and `g' can be used to
1067 specify kilo-, mega- and gigabytes, respectively. The nursery is the
1068 first generation (of two). A larger nursery will usually speed up the
1069 program but will obviously use more memory. The default nursery size
1072 \fBmajor=\fIcollector\fR
1073 Specifies which major collector to use. Options are `marksweep' for
1074 the Mark&Sweep collector, `marksweep-conc' for concurrent Mark&Sweep,
1075 `marksweep-par' for parallel Mark&Sweep, `marksweep-fixed' for
1076 Mark&Sweep with a fixed heap, and `marksweep-fixed-par' for parallel
1077 Mark&Sweep with a fixed heap. The Mark&Sweep collector is the default.
1079 \fBmajor-heap-size=\fIsize\fR
1080 Sets the size of the major heap (not including the large object space)
1081 for the fixed-heap Mark&Sweep collector (i.e. `marksweep-fixed' and
1082 `marksweep-fixed-par'). The size is in bytes, with optional suffixes
1083 `k', `m' and `g' to specify kilo-, mega- and gigabytes, respectively.
1084 The default is 512 megabytes.
1086 \fBsoft-heap-limit=\fIsize\fR
1087 Once the heap size gets larger than this size, ignore what the default
1088 major collection trigger metric says and only allow four nursery size's
1089 of major heap growth between major collections.
1091 \fBevacuation-threshold=\fIthreshold\fR
1092 Sets the evacuation threshold in percent. This option is only available
1093 on the Mark&Sweep major collectors. The value must be an
1094 integer in the range 0 to 100. The default is 66. If the sweep phase of
1095 the collection finds that the occupancy of a specific heap block type is
1096 less than this percentage, it will do a copying collection for that block
1097 type in the next major collection, thereby restoring occupancy to close
1098 to 100 percent. A value of 0 turns evacuation off.
1100 \fB(no-)lazy-sweep\fR
1101 Enables or disables lazy sweep for the Mark&Sweep collector. If
1102 enabled, the sweep phase of the garbage collection is done piecemeal
1103 whenever the need arises, typically during nursery collections. Lazy
1104 sweeping is enabled by default.
1106 \fBstack-mark=\fImark-mode\fR
1107 Specifies how application threads should be scanned. Options are
1108 `precise` and `conservative`. Precise marking allow the collector
1109 to know what values on stack are references and what are not.
1110 Conservative marking threats all values as potentially references
1111 and leave them untouched. Precise marking reduces floating garbage
1112 and can speed up nursery collection and allocation rate, it has
1113 the downside of requiring a significant extra memory per compiled
1114 method. The right option, unfortunately, requires experimentation.
1116 \fBsave-target-ratio=\fIratio\fR
1117 Specifies the target save ratio for the major collector. The collector
1118 lets a given amount of memory to be promoted from the nursery due to
1119 minor collections before it triggers a major collection. This amount
1120 is based on how much memory it expects to free. It is represented as
1121 a ratio of the size of the heap after a major collection.
1122 Valid values are between 0.1 and 2.0. The default is 0.5.
1123 Smaller values will keep the major heap size smaller but will trigger
1124 more major collections. Likewise, bigger values will use more memory
1125 and result in less frequent major collections.
1126 This option is EXPERIMENTAL, so it might disappear in later versions of mono.
1128 \fBdefault-allowance-ratio=\fIratio\fR
1129 Specifies the default allocation allowance when the calculated size
1130 is too small. The allocation allowance is how much memory the collector
1131 let be promoted before triggered a major collection.
1132 It is a ratio of the nursery size.
1133 Valid values are between 1.0 and 10.0. The default is 4.0.
1134 Smaller values lead to smaller heaps and more frequent major collections.
1135 Likewise, bigger values will allow the heap to grow faster but use
1136 more memory when it reaches a stable size.
1137 This option is EXPERIMENTAL, so it might disappear in later versions of mono.
1139 \fBminor=\fIminor-collector\fR
1140 Specifies which minor collector to use. Options are 'simple' which
1141 promotes all objects from the nursery directly to the old generation
1142 and 'split' which lets object stay longer on the nursery before promoting.
1144 \fBalloc-ratio=\fIratio\fR
1145 Specifies the ratio of memory from the nursery to be use by the alloc space.
1146 This only can only be used with the split minor collector.
1147 Valid values are integers between 1 and 100. Default is 60.
1149 \fBpromotion-age=\fIage\fR
1150 Specifies the required age of an object must reach inside the nursery before
1151 been promoted to the old generation. This only can only be used with the
1152 split minor collector.
1153 Valid values are integers between 1 and 14. Default is 2.
1155 \fB(no-)cementing\fR
1156 Enables or disables cementing. This can dramatically shorten nursery
1157 collection times on some benchmarks where pinned objects are referred
1158 to from the major heap.
1163 When using Mono with the SGen garbage collector this environment
1164 variable can be used to turn on various debugging features of the
1165 collector. The value of this variable is a comma separated list of
1166 words. Do not use these options in production.
1171 Sets the debug level to the specified number.
1173 \fBprint-allowance\fR
1174 After each major collection prints memory consumption for before and
1175 after the collection and the allowance for the minor collector, i.e. how
1176 much the heap is allowed to grow from minor collections before the next
1177 major collection is triggered.
1180 Gathers statistics on the classes whose objects are pinned in the
1181 nursery and for which global remset entries are added. Prints those
1182 statistics when shutting down.
1184 \fBcollect-before-allocs\fR
1186 \fBcheck-at-minor-collections\fR
1187 This performs a consistency check on minor collections and also clears
1188 the nursery at collection time, instead of the default, when buffers
1189 are allocated (clear-at-gc). The consistency check ensures that
1190 there are no major to minor references that are not on the remembered
1193 \fBmod-union-consistency-check\fR
1194 Checks that the mod-union cardtable is consistent before each
1195 finishing major collection pause. This check is only applicable to
1196 concurrent major collectors.
1198 \fBcheck-mark-bits\fR
1199 Checks that mark bits in the major heap are consistent at the end of
1200 each major collection. Consistent mark bits mean that if an object is
1201 marked, all objects that it had references to must also be marked.
1203 \fBcheck-nursery-pinned\fR
1204 After nursery collections, and before starting concurrent collections,
1205 check whether all nursery objects are pinned, or not pinned -
1206 depending on context. Does nothing when the split nursery collector
1209 \fBxdomain-checks\fR
1210 Performs a check to make sure that no references are left to an
1214 This clears the nursery at GC time instead of doing it when the thread
1215 local allocation buffer (TLAB) is created. The default is to clear
1216 the nursery at TLAB creation time.
1219 Don't do minor collections. If the nursery is full, a major collection
1220 is triggered instead, unless it, too, is disabled.
1223 Don't do major collections.
1225 \fBconservative-stack-mark\fR
1226 Forces the GC to scan the stack conservatively, even if precise
1227 scanning is available.
1229 \fBno-managed-allocator\fR
1230 Disables the managed allocator.
1232 \fBcheck-scan-starts\fR
1233 If set, does a plausibility check on the scan_starts before and after each collection
1235 \fBverify-nursery-at-minor-gc\fR
1236 If set, does a complete object walk of the nursery at the start of each minor collection.
1238 \fBdump-nursery-at-minor-gc\fR
1239 If set, dumps the contents of the nursery at the start of each minor collection. Requires
1240 verify-nursery-at-minor-gc to be set.
1242 \fBheap-dump=\fIfile\fR
1243 Dumps the heap contents to the specified file. To visualize the
1244 information, use the mono-heapviz tool.
1246 \fBbinary-protocol=\fIfile\fR
1247 Outputs the debugging output to the specified file. For this to
1248 work, Mono needs to be compiled with the BINARY_PROTOCOL define on
1249 sgen-gc.c. You can then use this command to explore the output
1251 sgen-grep-binprot 0x1234 0x5678 < file
1256 \fBMONO_GAC_PREFIX\fR
1257 Provides a prefix the runtime uses to look for Global Assembly Caches.
1258 Directories are separated by the platform path separator (colons on
1259 unix). MONO_GAC_PREFIX should point to the top directory of a prefixed
1260 install. Or to the directory provided in the gacutil /gacdir command. Example:
1261 .B /home/username/.mono:/usr/local/mono/
1264 Enables some filename rewriting support to assist badly-written
1265 applications that hard-code Windows paths. Set to a colon-separated
1266 list of "drive" to strip drive letters, or "case" to do
1267 case-insensitive file matching in every directory in a path. "all"
1268 enables all rewriting methods. (Backslashes are always mapped to
1269 slashes if this variable is set to a valid option).
1272 For example, this would work from the shell:
1275 MONO_IOMAP=drive:case
1279 If you are using mod_mono to host your web applications, you can use
1282 directive instead, like this:
1285 MonoIOMAP <appalias> all
1288 See mod_mono(8) for more details.
1290 Additionally. Mono includes a profiler module which allows one to track what
1291 adjustements to file paths IOMAP code needs to do. The tracking code reports
1292 the managed location (full stack trace) from which the IOMAP-ed call was made and,
1293 on process exit, the locations where all the IOMAP-ed strings were created in
1294 managed code. The latter report is only approximate as it is not always possible
1295 to estimate the actual location where the string was created. The code uses simple
1296 heuristics - it analyzes stack trace leading back to the string allocation location
1297 and ignores all the managed code which lives in assemblies installed in GAC as well as in the
1298 class libraries shipped with Mono (since they are assumed to be free of case-sensitivity
1299 issues). It then reports the first location in the user's code - in most cases this will be
1300 the place where the string is allocated or very close to the location. The reporting code
1301 is implemented as a custom profiler module (see the "PROFILING" section) and can be loaded
1302 in the following way:
1307 mono --profile=iomap yourapplication.exe
1310 Note, however, that Mono currently supports only one profiler module
1314 When Mono is using the LLVM code generation backend you can use this
1315 environment variable to pass code generation options to the LLVM
1318 \fBMONO_MANAGED_WATCHER\fR
1319 If set to "disabled", System.IO.FileSystemWatcher will use a file watcher
1320 implementation which silently ignores all the watching requests.
1321 If set to any other value, System.IO.FileSystemWatcher will use the default
1322 managed implementation (slow). If unset, mono will try to use inotify, FAM,
1323 Gamin, kevent under Unix systems and native API calls on Windows, falling
1324 back to the managed implementation on error.
1326 \fBMONO_MESSAGING_PROVIDER\fR
1327 Mono supports a plugin model for its implementation of System.Messaging making
1328 it possible to support a variety of messaging implementations (e.g. AMQP, ActiveMQ).
1329 To specify which messaging implementation is to be used the evironement variable
1330 needs to be set to the full class name for the provider. E.g. to use the RabbitMQ based
1331 AMQP implementation the variable should be set to:
1334 Mono.Messaging.RabbitMQ.RabbitMQMessagingProvider,Mono.Messaging.RabbitMQ
1337 If set causes the mono process to be bound to a single processor. This may be
1338 useful when debugging or working around race conditions.
1341 Disable inlining of thread local accesses. Try setting this if you get a segfault
1342 early on in the execution of mono.
1345 Provides a search path to the runtime where to look for library
1346 files. This is a tool convenient for debugging applications, but
1347 should not be used by deployed applications as it breaks the assembly
1348 loader in subtle ways.
1350 Directories are separated by the platform path separator (colons on unix). Example:
1351 .B /home/username/lib:/usr/local/mono/lib
1353 Alternative solutions to MONO_PATH include: installing libraries into
1354 the Global Assembly Cache (see gacutil(1)) or having the dependent
1355 libraries side-by-side with the main executable.
1357 For a complete description of recommended practices for application
1359 http://www.mono-project.com/Guidelines:Application_Deployment
1362 Experimental RTC support in the statistical profiler: if the user has
1363 the permission, more accurate statistics are gathered. The MONO_RTC
1364 value must be restricted to what the Linux rtc allows: power of two
1365 from 64 to 8192 Hz. To enable higher frequencies like 4096 Hz, run as root:
1368 echo 4096 > /proc/sys/dev/rtc/max-user-freq
1375 MONO_RTC=4096 mono --profiler=default:stat program.exe
1379 \fBMONO_SHARED_DIR\fR
1380 If set its the directory where the ".wapi" handle state is stored.
1381 This is the directory where the Windows I/O Emulation layer stores its
1382 shared state data (files, events, mutexes, pipes). By default Mono
1383 will store the ".wapi" directory in the users's home directory.
1385 \fBMONO_SHARED_HOSTNAME\fR
1386 Uses the string value of this variable as a replacement for the host name when
1387 creating file names in the ".wapi" directory. This helps if the host name of
1388 your machine is likely to be changed when a mono application is running or if
1389 you have a .wapi directory shared among several different computers.
1391 Mono typically uses the hostname to create the files that are used to
1392 share state across multiple Mono processes. This is done to support
1393 home directories that might be shared over the network.
1395 \fBMONO_STRICT_IO_EMULATION\fR
1396 If set, extra checks are made during IO operations. Currently, this
1397 includes only advisory locks around file writes.
1400 The name of the theme to be used by Windows.Forms. Available themes today
1401 include "clearlooks", "nice" and "win32".
1403 The default is "win32".
1405 \fBMONO_TLS_SESSION_CACHE_TIMEOUT\fR
1406 The time, in seconds, that the SSL/TLS session cache will keep it's entry to
1407 avoid a new negotiation between the client and a server. Negotiation are very
1408 CPU intensive so an application-specific custom value may prove useful for
1409 small embedded systems.
1411 The default is 180 seconds.
1413 \fBMONO_THREADS_PER_CPU\fR
1414 The maximum number of threads in the general threadpool will be
1415 20 + (MONO_THREADS_PER_CPU * number of CPUs). The default value for this
1418 \fBMONO_XMLSERIALIZER_THS\fR
1419 Controls the threshold for the XmlSerializer to produce a custom
1420 serializer for a given class instead of using the Reflection-based
1421 interpreter. The possible values are `no' to disable the use of a
1422 custom serializer or a number to indicate when the XmlSerializer
1423 should start serializing. The default value is 50, which means that
1424 the a custom serializer will be produced on the 50th use.
1426 \fBMONO_X509_REVOCATION_MODE\fR
1427 Sets the revocation mode used when validating a X509 certificate chain (https,
1428 ftps, smtps...). The default is 'nocheck', which performs no revocation check
1429 at all. The other possible values are 'offline', which performs CRL check (not
1430 implemented yet) and 'online' which uses OCSP and CRL to verify the revocation
1431 status (not implemented yet).
1432 .SH ENVIRONMENT VARIABLES FOR DEBUGGING
1434 \fBMONO_ASPNET_NODELETE\fR
1435 If set to any value, temporary source files generated by ASP.NET support
1436 classes will not be removed. They will be kept in the user's temporary
1440 If set, enables some features of the runtime useful for debugging.
1441 This variable should contain a comma separated list of debugging options.
1442 Currently, the following options are supported:
1446 \fBbreak-on-unverified\fR
1447 If this variable is set, when the Mono VM runs into a verification
1448 problem, instead of throwing an exception it will break into the
1449 debugger. This is useful when debugging verifier problems
1452 This option can be used to get more detailed information from
1453 InvalidCast exceptions, it will provide information about the types
1456 \fBcollect-pagefault-stats\fR
1457 Collects information about pagefaults. This is used internally to
1458 track the number of page faults produced to load metadata. To display
1459 this information you must use this option with "--stats" command line
1462 \fBdont-free-domains\fR
1463 This is an Optimization for multi-AppDomain applications (most
1464 commonly ASP.NET applications). Due to internal limitations Mono,
1465 Mono by default does not use typed allocations on multi-appDomain
1466 applications as they could leak memory when a domain is unloaded.
1468 Although this is a fine default, for applications that use more than
1469 on AppDomain heavily (for example, ASP.NET applications) it is worth
1470 trading off the small leaks for the increased performance
1471 (additionally, since ASP.NET applications are not likely going to
1472 unload the application domains on production systems, it is worth
1473 using this feature).
1475 \fBdyn-runtime-invoke\fR
1476 Instructs the runtime to try to use a generic runtime-invoke wrapper
1477 instead of creating one invoke wrapper.
1480 Equivalent to setting the \fBMONO_XDEBUG\fR variable, this emits
1481 symbols into a shared library as the code is JITed that can be loaded
1482 into GDB to inspect symbols.
1484 \fBgen-seq-points\fR
1485 Automatically generates sequence points where the
1486 IL stack is empty. These are places where the debugger can set a
1489 \fBexplicit-null-checks\fR
1490 Makes the JIT generate an explicit NULL check on variable dereferences
1491 instead of depending on the operating system to raise a SIGSEGV or
1492 another form of trap event when an invalid memory location is
1496 Captures the interrupt signal (Control-C) and displays a stack trace
1497 when pressed. Useful to find out where the program is executing at a
1498 given point. This only displays the stack trace of a single thread.
1501 Instructs the runtime to initialize the stack with
1502 some known values (0x2a on x86-64) at the start of a method to assist
1503 in debuggin the JIT engine.
1505 \fBkeep-delegates\fR
1506 This option will leak delegate trampolines that are no longer
1507 referenced as to present the user with more information about a
1508 delegate misuse. Basically a delegate instance might be created,
1509 passed to unmanaged code, and no references kept in managed code,
1510 which will garbage collect the code. With this option it is possible
1511 to track down the source of the problems.
1513 \fBreverse-pinvoke-exceptions
1514 This option will cause mono to abort with a descriptive message when
1515 during stack unwinding after an exception it reaches a native stack
1516 frame. This happens when a managed delegate is passed to native code,
1517 and the managed delegate throws an exception. Mono will normally try
1518 to unwind the stack to the first (managed) exception handler, and it
1519 will skip any native stack frames in the process. This leads to
1520 undefined behaviour (since mono doesn't know how to process native
1521 frames), leaks, and possibly crashes too.
1523 \fBno-gdb-backtrace\fR
1524 This option will disable the GDB backtrace emitted by the runtime
1525 after a SIGSEGV or SIGABRT in unmanaged code.
1527 \fBsuspend-on-sigsegv\fR
1528 This option will suspend the program when a native SIGSEGV is received.
1529 This is useful for debugging crashes which do not happen under gdb,
1530 since a live process contains more information than a core file.
1534 \fBMONO_LOG_LEVEL\fR
1535 The logging level, possible values are `error', `critical', `warning',
1536 `message', `info' and `debug'. See the DEBUGGING section for more
1540 Controls the domain of the Mono runtime that logging will apply to.
1541 If set, the log mask is changed to the set value. Possible values are
1542 "asm" (assembly loader), "type", "dll" (native library loader), "gc"
1543 (garbage collector), "cfg" (config file loader), "aot" (precompiler),
1544 "security" (e.g. Moonlight CoreCLR support) and "all".
1545 The default value is "all". Changing the mask value allows you to display only
1546 messages for a certain component. You can use multiple masks by comma
1547 separating them. For example to see config file messages and assembly loader
1548 messages set you mask to "asm,cfg".
1551 Used for runtime tracing of method calls. The format of the comma separated
1560 disabled Trace output off upon start.
1563 You can toggle trace output on/off sending a SIGUSR2 signal to the program.
1565 \fBMONO_TRACE_LISTENER\fR
1566 If set, enables the System.Diagnostics.DefaultTraceListener, which will
1567 print the output of the System.Diagnostics Trace and Debug classes.
1568 It can be set to a filename, and to Console.Out or Console.Error to display
1569 output to standard output or standard error, respectively. If it's set to
1570 Console.Out or Console.Error you can append an optional prefix that will
1571 be used when writing messages like this: Console.Error:MyProgramName.
1572 See the System.Diagnostics.DefaultTraceListener documentation for more
1575 \fBMONO_WCF_TRACE\fR
1576 This eases WCF diagnostics functionality by simply outputs all log messages from WCF engine to "stdout", "stderr" or any file passed to this environment variable. The log format is the same as usual diagnostic output.
1578 \fBMONO_XEXCEPTIONS\fR
1579 This throws an exception when a X11 error is encountered; by default a
1580 message is displayed but execution continues
1582 \fBMONO_XMLSERIALIZER_DEBUG\fR
1583 Set this value to 1 to prevent the serializer from removing the
1584 temporary files that are created for fast serialization; This might
1585 be useful when debugging.
1588 This is used in the System.Windows.Forms implementation when running
1589 with the X11 backend. This is used to debug problems in Windows.Forms
1590 as it forces all of the commands send to X11 server to be done
1591 synchronously. The default mode of operation is asynchronous which
1592 makes it hard to isolate the root of certain problems.
1594 \fBMONO_GENERIC_SHARING\fR
1595 This environment variable controls the kind of generic sharing used.
1596 This variable is used by internal JIT developers and should not be
1597 changed in production. Do not use it.
1599 The variable controls which classes will have generic code sharing
1602 Permissible values are:
1606 All generated code can be shared.
1609 Only the classes in System.Collections.Generic will have its code
1610 shared (this is the default value).
1613 Only code in corlib will have its code shared.
1616 No generic code sharing will be performed.
1619 Generic code sharing by default only applies to collections. The
1620 Mono JIT by default turns this on.
1623 When the the MONO_XDEBUG env var is set, debugging info for JITted
1624 code is emitted into a shared library, loadable into gdb. This enables,
1625 for example, to see managed frame names on gdb backtraces.
1627 \fBMONO_VERBOSE_METHOD\fR
1628 Enables the maximum JIT verbosity for the specified method. This is
1629 very helpfull to diagnose a miscompilation problems of a specific
1632 \fBMONO_VERBOSE_HWCAP\fR
1633 If set, makes the JIT output information about detected CPU features
1634 (such as SSE, CMOV, FCMOV, etc) to stdout.
1636 If you want to use Valgrind, you will find the file `mono.supp'
1637 useful, it contains the suppressions for the GC which trigger
1638 incorrect warnings. Use it like this:
1640 valgrind --suppressions=mono.supp mono ...
1643 On some platforms, Mono can expose a set of DTrace probes (also known
1644 as user-land statically defined, USDT Probes).
1646 They are defined in the file `mono.d'.
1648 .B ves-init-begin, ves-init-end
1650 Begin and end of runtime initialization.
1652 .B method-compile-begin, method-compile-end
1654 Begin and end of method compilation.
1655 The probe arguments are class name, method name and signature,
1656 and in case of method-compile-end success or failure of compilation.
1660 Begin and end of Garbage Collection.
1662 To verify the availability of the probes, run:
1664 dtrace -P mono'$target' -l -c mono
1667 Mono's Ping implementation for detecting network reachability can
1668 create the ICMP packets itself without requiring the system ping
1669 command to do the work. If you want to enable this on Linux for
1670 non-root users, you need to give the Mono binary special permissions.
1672 As root, run this command:
1674 # setcap cap_net_raw=+ep /usr/bin/mono
1677 On Unix assemblies are loaded from the installation lib directory. If you set
1678 `prefix' to /usr, the assemblies will be located in /usr/lib. On
1679 Windows, the assemblies are loaded from the directory where mono and
1682 .B ~/.mono/aot-cache
1684 The directory for the ahead-of-time compiler demand creation
1685 assemblies are located.
1687 .B /etc/mono/config, ~/.mono/config
1689 Mono runtime configuration file. See the mono-config(5) manual page
1690 for more information.
1692 .B ~/.config/.mono/certs, /usr/share/.mono/certs
1694 Contains Mono certificate stores for users / machine. See the certmgr(1)
1695 manual page for more information on managing certificate stores and
1696 the mozroots(1) page for information on how to import the Mozilla root
1697 certificates into the Mono certificate store.
1699 .B ~/.mono/assemblies/ASSEMBLY/ASSEMBLY.config
1701 Files in this directory allow a user to customize the configuration
1702 for a given system assembly, the format is the one described in the
1703 mono-config(5) page.
1705 .B ~/.config/.mono/keypairs, /usr/share/.mono/keypairs
1707 Contains Mono cryptographic keypairs for users / machine. They can be
1708 accessed by using a CspParameters object with DSACryptoServiceProvider
1709 and RSACryptoServiceProvider classes.
1711 .B ~/.config/.isolatedstorage, ~/.local/share/.isolatedstorage, /usr/share/.isolatedstorage
1713 Contains Mono isolated storage for non-roaming users, roaming users and
1714 local machine. Isolated storage can be accessed using the classes from
1715 the System.IO.IsolatedStorage namespace.
1717 .B <assembly>.config
1719 Configuration information for individual assemblies is loaded by the
1720 runtime from side-by-side files with the .config files, see the
1721 http://www.mono-project.com/Config for more information.
1723 .B Web.config, web.config
1725 ASP.NET applications are configured through these files, the
1726 configuration is done on a per-directory basis. For more information
1727 on this subject see the http://www.mono-project.com/Config_system.web
1730 Mailing lists are listed at the
1731 http://www.mono-project.com/Mailing_Lists
1733 http://www.mono-project.com
1736 certmgr(1), csharp(1), mcs(1), mdb(1), monocov(1), monodis(1),
1737 mono-config(5), mozroots(1), mprof-report(1), pdb2mdb(1), xsp(1), mod_mono(8).
1739 For more information on AOT:
1740 http://www.mono-project.com/AOT
1742 For ASP.NET-related documentation, see the xsp(1) manual page
projects / mono.git / blob