2008-04-22 Robert Jordan <robertj@gmx.net>

	* mono.1: Document MONO_DEBUG=no-gdb-backtrace.

svn path=/trunk/mono/; revision=101489

diff --git a/man/ChangeLog b/man/ChangeLog
index 9e3c647e085ca8d8ef3bead4224906151df3c778..aa42ef7e4a1c8c2d28b05aa38530f2e78c747a65 100644 (file)
--- a/man/ChangeLog
+++ b/man/ChangeLog
@@ -1,3 +1,7 @@
+2008-04-22  Robert Jordan  <robertj@gmx.net>
+
+       * mono.1: Document MONO_DEBUG=no-gdb-backtrace.
+
 2008-04-21  Martin Baulig  <martin@ximian.com>
 
        * mono.1: Documented the new --debug=mdb-optimizations option.

diff --git a/man/mono.1 b/man/mono.1
index d55737ec4292db4c4a4d5a1a00c87c20996fb359..73fc72fd7380f7bb0dc6a664d8975dfb333ff722 100644 (file)
--- a/man/mono.1
+++ b/man/mono.1
@@ -775,6 +775,10 @@ to track down the source of the problems.
 If this variable is set, when the Mono VM runs into a verification
 problem, instead of throwing an exception it will break into the
 debugger.  This is useful when debugging verifier problems
+.TP
+.I "no-gdb-backtrace"
+This option will disable the GDB backtrace emitted by the runtime
+after a SIGSEGV or SIGABRT in unmanaged code.
 .ne
 .RE
 .TP