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 1ae9fb9d996fb54b68c914a9dacbb9e085ef0ba2..dff9d042be93a74e0d7180147950fffb8b6069a8 100755 (executable)
--- 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;