From d22d540c326f4964566f1c3dcb72df7986782215 Mon Sep 17 00:00:00 2001 From: Jeremy Allison Date: Fri, 14 Jul 2006 23:23:39 +0000 Subject: r17041: Trying to track down a *big* memory leak in the new lock code. Fix a small one first.... (easy to valgrind). Jeremy (This used to be commit 43d24fbd41ed745a5b21514b526e655663c509ee) --- 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 e99d4ab900..376c2e30ba 100644 --- a/source3/locking/brlock.c +++ b/source3/locking/brlock.c @@ -1259,7 +1259,7 @@ void brl_close_fnum(struct byte_range_lock *br_lck) /* Copy the current lock array. */ locks_copy = TALLOC_MEMDUP(br_lck, locks, br_lck->num_locks * sizeof(struct lock_struct)); if (!locks_copy) { - DEBUG(0,("brl_close_fnum: talloc fail.\n")); + smb_panic("brl_close_fnum: talloc fail.\n"); } for (i=0; i < br_lck->num_locks; i++) { -- cgit