You've already forked linux-packaging-mono
Imported Upstream version 4.2.0.179
Former-commit-id: 0a113cb3a6feb7873f632839b1307cc6033cd595
This commit is contained in:
committed by
Jo Shields
parent
183bba2c9a
commit
6992685b86
@@ -56,6 +56,7 @@ man_MANS = \
|
||||
xsd.1 \
|
||||
mono-configuration-crypto.1 \
|
||||
ccrewrite.1 \
|
||||
cccheck.1
|
||||
cccheck.1 \
|
||||
mono-symbolicate.1
|
||||
|
||||
EXTRA_DIST = $(man_MANS)
|
||||
|
@@ -415,7 +415,8 @@ man_MANS = \
|
||||
xsd.1 \
|
||||
mono-configuration-crypto.1 \
|
||||
ccrewrite.1 \
|
||||
cccheck.1
|
||||
cccheck.1 \
|
||||
mono-symbolicate.1
|
||||
|
||||
EXTRA_DIST = $(man_MANS)
|
||||
all: all-am
|
||||
|
@@ -20,6 +20,26 @@ revocation lists (CRL) or certificate trust lists (CTL) to/from a
|
||||
certificate store. Certificate stores are used to build and validate
|
||||
certificate chains for Authenticode(r) code signing validation and SSL
|
||||
server certificates.
|
||||
.SH STORES
|
||||
The
|
||||
.I store
|
||||
represents the certificate store to use. It can be one of the
|
||||
following:
|
||||
.TP
|
||||
.I "My"
|
||||
This is the personal certificate store.
|
||||
.TP
|
||||
.I "AddressBook"
|
||||
This is the store for other people.
|
||||
.TP
|
||||
.I "CA"
|
||||
This is a store for intermediate certificate authorities.
|
||||
.TP
|
||||
.I "Trust"
|
||||
This is for trusted roots.
|
||||
.TP
|
||||
.I "Disallowed"
|
||||
This is for untrusted roots
|
||||
.SH ACTIONS
|
||||
.TP
|
||||
.I "-list"
|
||||
|
23
man/mcs.1
23
man/mcs.1
@@ -249,29 +249,6 @@ This will instruct the compiler to reference the System.* libraries
|
||||
available on a typical dotnet framework installation, notice that this
|
||||
does not include all of the Mono libraries, only the System.* ones. This
|
||||
is a convenient shortcut for those porting code.
|
||||
.TP
|
||||
.I \-pkg:olive
|
||||
Use this to reference the "Olive" libraries (the 3.0 and 3.5 extended
|
||||
libraries).
|
||||
.TP
|
||||
.I \-pkg:silver
|
||||
References the assemblies for creating Moonlight/Silverlight
|
||||
applications.
|
||||
.TP
|
||||
.I \-pkg:silverdesktop
|
||||
Use this option to create Moonlight/Silverlight applications that
|
||||
target the desktop. This option allows developers to consume the
|
||||
Silverlight APIs with the full 2.0 profile API available to them,
|
||||
unlike
|
||||
.I smcs
|
||||
it gives full access to all the APIs that are part of Mono. The only
|
||||
downside is that applications created with silverdesktop will not run
|
||||
on the browser. Typically these applications will be launched
|
||||
with the
|
||||
.I mopen
|
||||
command line tool.
|
||||
.TP
|
||||
For more details see the PACKAGE section in this document
|
||||
.ne
|
||||
.RE
|
||||
.TP
|
||||
|
39
man/mono-symbolicate.1
Normal file
39
man/mono-symbolicate.1
Normal file
@@ -0,0 +1,39 @@
|
||||
.\"
|
||||
.\" mono-symbolicate manual page.
|
||||
.\" Copyright 2015 Xamarin
|
||||
.\" Author:
|
||||
.\" Marcos Henrich <marcos.henrich@xamarin.com>
|
||||
.\"
|
||||
.TH "mono-symbolicate" 1
|
||||
.SH NAME
|
||||
mono-symbolicate \- Mono Symbolicate Tool
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B mono-symbolicate exefile stacktracesfile [directories...]
|
||||
.SH DESCRIPTION
|
||||
mono-symbolicate is a tool that converts a stack trace with <filename unknown>:0
|
||||
into one with file names and line numbers.
|
||||
.PP
|
||||
The output of calling this tool will be the provided
|
||||
.I stacktracesfile
|
||||
where <filename unknown>:0 parts are replaced by
|
||||
a file name and a line number.
|
||||
.PP
|
||||
For the tool to work it needs to load referenced assemblies, it will first look
|
||||
in the same folder as
|
||||
.I exefile
|
||||
then from one of the provided
|
||||
.I directories.
|
||||
.PP
|
||||
The tool assumes that the folder with a referenced assembly called for example
|
||||
name.dll will also include name.dll.mdb,
|
||||
if the referenced assembly is AOT compiled then the tool is also expecting to find
|
||||
name.dll.msym.
|
||||
.SH AUTHOR
|
||||
Written by Marcos Henrich
|
||||
.SH COPYRIGHT
|
||||
Copyright (C) 2015 Xamarin.
|
||||
.SH MAILING LISTS
|
||||
Visit http://lists.ximian.com/mailman/listinfo/mono-devel-list for details.
|
||||
.SH WEB SITE
|
||||
Visit http://www.mono-project.com for details
|
85
man/mono.1
85
man/mono.1
@@ -146,6 +146,13 @@ Defaults to 128.
|
||||
.I nodebug
|
||||
Instructs the AOT compiler to not output any debugging information.
|
||||
.TP
|
||||
.I no-direct-calls
|
||||
This prevents the AOT compiler from generating a direct calls to a
|
||||
method. The AOT compiler usually generates direct calls for certain
|
||||
methods that do not require going through the PLT (for example,
|
||||
methods that are known to not require a hook like a static
|
||||
constructor) or call into simple internal calls.
|
||||
.TP
|
||||
.I dwarfdebug
|
||||
Instructs the AOT compiler to emit DWARF debugging information. When
|
||||
used together with the nodebug option, only DWARF debugging
|
||||
@@ -333,31 +340,31 @@ In general, Mono has been tuned to use the default set of flags,
|
||||
before using these flags for a deployment setting, you might want to
|
||||
actually measure the benefits of using them.
|
||||
.Sp
|
||||
The following optimizations are implemented:
|
||||
The following optimization flags are implemented in the core engine:
|
||||
.nf
|
||||
abcrem Array bound checks removal
|
||||
all Turn on all optimizations
|
||||
peephole Peephole postpass
|
||||
aot Usage of Ahead Of Time compiled code
|
||||
branch Branch optimizations
|
||||
inline Inline method calls
|
||||
cfold Constant folding
|
||||
cmov Conditional moves [arch-dependency]
|
||||
deadce Dead code elimination
|
||||
consprop Constant propagation
|
||||
copyprop Copy propagation
|
||||
deadce Dead code elimination
|
||||
linears Linear scan global reg allocation
|
||||
cmov Conditional moves [arch-dependency]
|
||||
shared Emit per-domain code
|
||||
sched Instruction scheduling
|
||||
intrins Intrinsic method implementations
|
||||
tailc Tail recursion and tail calls
|
||||
loop Loop related optimizations
|
||||
fcmov Fast x86 FP compares [arch-dependency]
|
||||
leaf Leaf procedures optimizations
|
||||
aot Usage of Ahead Of Time compiled code
|
||||
precomp Precompile all methods before executing Main
|
||||
abcrem Array bound checks removal
|
||||
ssapre SSA based Partial Redundancy Elimination
|
||||
sse2 SSE2 instructions on x86 [arch-dependency]
|
||||
float32 Perform 32-bit float arithmetic using 32-bit operations
|
||||
gshared Enable generic code sharing.
|
||||
inline Inline method calls
|
||||
intrins Intrinsic method implementations
|
||||
linears Linear scan global reg allocation
|
||||
leaf Leaf procedures optimizations
|
||||
loop Loop related optimizations
|
||||
peephole Peephole postpass
|
||||
precomp Precompile all methods before executing Main
|
||||
sched Instruction scheduling
|
||||
shared Emit per-domain code
|
||||
sse2 SSE2 instructions on x86 [arch-dependency]
|
||||
tailc Tail recursion and tail calls
|
||||
.fi
|
||||
.Sp
|
||||
For example, to enable all the optimization but dead code
|
||||
@@ -370,6 +377,23 @@ The flags that are flagged with [arch-dependency] indicate that the
|
||||
given option if used in combination with Ahead of Time compilation
|
||||
(--aot flag) would produce pre-compiled code that will depend on the
|
||||
current CPU and might not be safely moved to another computer.
|
||||
.RS
|
||||
.ne 8
|
||||
.PP
|
||||
The following optimizations are supported
|
||||
.TP
|
||||
.I float32
|
||||
Requests that the runtime performn 32-bit floating point operations
|
||||
using only 32-bits. By default the Mono runtime tries to use the
|
||||
highest precision available for floating point operations, but while
|
||||
this might render better results, the code might run slower. This
|
||||
options also affects the code generated by the LLVM backend.
|
||||
.TP
|
||||
.I inline
|
||||
Controls whether the runtime should attempt to inline (the default),
|
||||
or not inline methods invocations
|
||||
.ne
|
||||
.RE
|
||||
.TP
|
||||
\fB--runtime=VERSION\fR
|
||||
Mono supports different runtime versions. The version used depends on the program
|
||||
@@ -393,10 +417,6 @@ Using security without parameters is equivalent as calling it with the
|
||||
"cas" parameter.
|
||||
.PP
|
||||
The following modes are supported:
|
||||
.TP
|
||||
.I cas
|
||||
This allows mono to support declarative security attributes,
|
||||
e.g. execution of Code Access Security (CAS) or non-CAS demands.
|
||||
.TP
|
||||
.I core-clr
|
||||
Enables the core-clr security system, typically used for
|
||||
@@ -1122,9 +1142,16 @@ to 100 percent. A value of 0 turns evacuation off.
|
||||
.TP
|
||||
\fB(no-)lazy-sweep\fR
|
||||
Enables or disables lazy sweep for the Mark&Sweep collector. If
|
||||
enabled, the sweep phase of the garbage collection is done piecemeal
|
||||
whenever the need arises, typically during nursery collections. Lazy
|
||||
sweeping is enabled by default.
|
||||
enabled, the sweeping of individual major heap blocks is done
|
||||
piecemeal whenever the need arises, typically during nursery
|
||||
collections. Lazy sweeping is enabled by default.
|
||||
.TP
|
||||
\fB(no-)concurrent-sweep\fR
|
||||
Enables or disables concurrent sweep for the Mark&Sweep collector. If
|
||||
enabled, the iteration of all major blocks to determine which ones can
|
||||
be freed and which ones have to be kept and swept, is done
|
||||
concurrently with the running program. Concurrent sweeping is enabled
|
||||
by default.
|
||||
.TP
|
||||
\fBstack-mark=\fImark-mode\fR
|
||||
Specifies how application threads should be scanned. Options are
|
||||
@@ -1283,14 +1310,13 @@ work, Mono needs to be compiled with the BINARY_PROTOCOL define on
|
||||
sgen-gc.c. You can then use this command to explore the output
|
||||
.nf
|
||||
sgen-grep-binprot 0x1234 0x5678 < file
|
||||
.fi
|
||||
.TP
|
||||
\fBnursery-canaries\fR
|
||||
If set, objects allocated in the nursery are suffixed with a canary (guard)
|
||||
word, which is checked on each minor collection. Can be used to detect/debug
|
||||
heap corruption issues.
|
||||
.fi
|
||||
.ne
|
||||
.RE
|
||||
|
||||
.TP
|
||||
\fBdo-not-finalize\fR
|
||||
If enabled, finalizers will not be run. Everything else will be
|
||||
@@ -1298,7 +1324,10 @@ unaffected: finalizable objects will still be put into the
|
||||
finalization queue where they survive until they're scheduled to
|
||||
finalize. Once they're not in the queue anymore they will be
|
||||
collected regularly.
|
||||
.fi
|
||||
|
||||
.TP
|
||||
\fBlog-finalizers\fR
|
||||
Log verbosely around the finalization process to aid debugging.
|
||||
.ne
|
||||
.RE
|
||||
.TP
|
||||
|
@@ -337,6 +337,10 @@ version
|
||||
.IP \[bu] 2
|
||||
\f[I]thread\f[]: thread information
|
||||
.IP \[bu] 2
|
||||
\f[I]domain\f[]: app domain information
|
||||
.IP \[bu] 2
|
||||
\f[I]context\f[]: remoting context information
|
||||
.IP \[bu] 2
|
||||
\f[I]heapshot\f[]: live heap usage at heap shots
|
||||
.IP \[bu] 2
|
||||
\f[I]counters\f[]: counters samples
|
||||
|
8
man/sn.1
8
man/sn.1
@@ -71,8 +71,8 @@ Convert the input file to a CSV file (using hexadecimal).
|
||||
.SH STRONGNAME SIGNING OPTIONS
|
||||
.TP
|
||||
.I "-D assembly1 assembly2"
|
||||
Compare if assembly1 and assembly are the same exception for their signature.
|
||||
This is done by comparing the hash of the metadata of both assembly.
|
||||
Compare if assembly1 and assembly2 are the same except for their signature.
|
||||
This is done by comparing the hash of the metadata of both assemblies.
|
||||
.TP
|
||||
.I "-k [size] keypair.snk"
|
||||
Create a new strongname keypair in the specified file. The default key
|
||||
@@ -85,7 +85,7 @@ even if it's possible, to use length lesser than 1024 bits.
|
||||
.I "-R assembly keypair.snk"
|
||||
Re-sign the specified assembly using the specified strongname keypair file
|
||||
(SNK) or a PKCS#12/PFX password protected file. You can only sign an
|
||||
assembly with the private key that match the public key inside the assembly
|
||||
assembly with the private key that matches the public key inside the assembly
|
||||
(unless it's public key token has been remapped in machine.config).
|
||||
.TP
|
||||
.I "-Rc assembly container"
|
||||
@@ -135,7 +135,7 @@ another public key for verification. This is useful in two scenarios. First,
|
||||
assemblies signed with the "ECMA key" need to be verified by the "runtime"
|
||||
key (as the ECMA key isn't a public key). Second, many assemblies are signed
|
||||
with private keys that Mono can't use (e.g. System.Security.dll assembly).
|
||||
A new key cannot be used because it should change thr strongname (a new key
|
||||
A new key cannot be used because it should change the strongname (a new key
|
||||
pair would have a new public key which would produce a new token). Public
|
||||
key token remapping is the solution for both problems. Each token must be
|
||||
configured in a "map" entry similar to this one: <map Token="b77a5c561934e089"
|
||||
|
Reference in New Issue
Block a user