lib/util: Call log_stack_trace() in smb_panic_default()

This matches the AD DC with the behaviour in smbd.

Signed-off-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
BUG: https://bugzilla.samba.org/show_bug.cgi?id=13454

Autobuild-User(master): Jeremy Allison <jra@samba.org>
Autobuild-Date(master): Wed Apr 11 04:03:07 CEST 2018 on sn-devel-144

(cherry picked from commit 462eb4a44cc51dc17aebbcd5c609c9ff7f088554)

Autobuild-User(v4-7-test): Karolin Seeger <kseeger@samba.org>
Autobuild-Date(v4-7-test): Mon Jun  4 14:20:17 CEST 2018 on sn-devel-144

diff --git a/lib/util/fault.c b/lib/util/fault.c
index e539aff9e7b4762092b01358628550abf66e0f70..1b56361aa62bf15d98e753744440b5927c9970d3 100644 (file)
--- a/lib/util/fault.c
+++ b/lib/util/fault.c
@@ -126,6 +126,7 @@ static void smb_panic_default(const char *why)
 {
        DBG_ERR("PANIC (pid %llu): %s\n",
                    (unsigned long long)getpid(), why);
+       log_stack_trace();
 
 #if defined(HAVE_PRCTL) && defined(PR_SET_PTRACER)
        /*
@@ -172,8 +173,6 @@ _PUBLIC_ void smb_panic(const char *why)
        smb_panic_default(why);
 }
 
-
-
 /*******************************************************************
  Print a backtrace of the stack to the debug log. This function
  DELIBERATELY LEAKS MEMORY. The expectation is that you should