diff options
author | Douglas Bagnall <douglas.bagnall@catalyst.net.nz> | 2021-02-11 22:19:31 +1300 |
---|---|---|
committer | David Mulder <dmulder@samba.org> | 2021-02-22 14:45:38 +0000 |
commit | 9e19b148f6c9d0800b08fe221c7f88a5d3ecf52d (patch) | |
tree | e833e6ef11c16f233f0aa65b0bf182762b19dc7c | |
parent | 80faba100dbf12d706a63e1a27758aefefae7793 (diff) | |
download | samba-9e19b148f6c9d0800b08fe221c7f88a5d3ecf52d.tar.gz |
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>
-rwxr-xr-x | selftest/target/Samba4.pm | 5 |
1 files changed, 5 insertions, 0 deletions
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; |