From b69041dadf00177c0f14f46f2983a6d1fad0350f Mon Sep 17 00:00:00 2001 From: Robert Jordan Date: Tue, 22 Apr 2008 20:36:07 +0000 Subject: [PATCH] 2008-04-22 Robert Jordan * mono.1: Document MONO_DEBUG=no-gdb-backtrace. svn path=/trunk/mono/; revision=101489 --- man/ChangeLog | 4 ++++ man/mono.1 | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/man/ChangeLog b/man/ChangeLog index 9e3c647e085..aa42ef7e4a1 100644 --- a/man/ChangeLog +++ b/man/ChangeLog @@ -1,3 +1,7 @@ +2008-04-22 Robert Jordan + + * mono.1: Document MONO_DEBUG=no-gdb-backtrace. + 2008-04-21 Martin Baulig * mono.1: Documented the new --debug=mdb-optimizations option. diff --git a/man/mono.1 b/man/mono.1 index d55737ec429..73fc72fd738 100644 --- 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 -- 2.25.1