From f58e6a997750c16e0c1ffccabbbf69469eb280c2 Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Sun, 21 Mar 2004 08:43:41 +0000 Subject: Given how often a panic has to do with malloc() problems, don't tempt things more by calling SAFE_FREE() just before we exit our panic handler. Andrew Bartlett (This used to be commit d0b820562b8a7f8e5d0224926d46590b9f1ca9a3) --- source3/lib/util.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'source3') diff --git a/source3/lib/util.c b/source3/lib/util.c index 10d224baab..3f57048a00 100644 --- a/source3/lib/util.c +++ b/source3/lib/util.c @@ -1411,7 +1411,7 @@ void smb_panic2(const char *why, BOOL decrement_pid_count ) for (i = 0; i < backtrace_size; i++) DEBUGADD(0, (" #%u %s\n", i, backtrace_strings[i])); - SAFE_FREE(backtrace_strings); + /* Leak the backtrace_strings, rather than risk what free() might do */ } #elif HAVE_LIBEXC -- cgit