From b067a5e4e83556d11a68ea1837ce4698762c123d Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Tue, 3 Nov 2009 10:59:18 +0100 Subject: s3: Remove debug_ctx() smbd just crashed on me: In a debug message I called a routine preparing a string that itself used debug_ctx. The outer routine also used it after the inner routine had returned. It was still referencing the talloc context that the outer debug_ctx() had given us, which the inner DEBUG had already freed. --- source3/locking/brlock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'source3/locking/brlock.c') diff --git a/source3/locking/brlock.c b/source3/locking/brlock.c index 18a798182b..c72fad7f2e 100644 --- a/source3/locking/brlock.c +++ b/source3/locking/brlock.c @@ -45,7 +45,7 @@ static void print_lock_struct(unsigned int i, struct lock_struct *pls) i, (unsigned int)pls->context.smbpid, (unsigned int)pls->context.tid, - procid_str(debug_ctx(), &pls->context.pid) )); + procid_str(talloc_tos(), &pls->context.pid) )); DEBUG(10,("start = %.0f, size = %.0f, fnum = %d, %s %s\n", (double)pls->start, -- cgit