From: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>
Date: Thu, 11 Feb 2021 09:19:31 +0000 (+1300)
Subject: selftest: preforkrestartdc doesn't need gdb-backtraces
X-Git-Tag: tevent-0.11.0~1736
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=9e19b148f6c9d0800b08fe221c7f88a5d3ecf52d;p=thirdparty%2Fsamba.git

selftest: preforkrestartdc doesn't need gdb-backtraces

There are tests in this environment that kill processes with SEGV
signals, which causes a backtrace that is entirely spurious from a
debugging point of view.

We can turn that off, saving processor time and moments of developer
confusion.

Signed-off-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>
Reviewed-by: David Mulder <dmulder@suse.com>
---

diff --git a/selftest/target/Samba4.pm b/selftest/target/Samba4.pm
index 1ae9fb9d996..dff9d042be9 100755
--- a/selftest/target/Samba4.pm
+++ b/selftest/target/Samba4.pm
@@ -2743,6 +2743,11 @@ sub setup_preforkrestartdc
 		return undef;
 	}
 
+        # We treat processes in this environment cruelly, sometimes
+        # sending them SIGSEGV signals. We don't need gdb_backtrace
+        # dissecting these fake crashes in precise detail.
+        $env->{PLEASE_NO_GDB_BACKTRACE} = '1';
+
 	$env->{NSS_WRAPPER_MODULE_SO_PATH} = undef;
 	$env->{NSS_WRAPPER_MODULE_FN_PREFIX} = undef;