From 19f14232872b602fedd4dcf6310080b4181e7e61 Mon Sep 17 00:00:00 2001 From: Augustin Cavalier Date: Wed, 12 Feb 2025 20:58:44 -0500 Subject: [PATCH] libroot/os: Re-enable "was not actually locked!" assertion. It was disabled because hoard2 triggered it far too often. But now that we're using OpenBSD malloc with different glue, this isn't an issue anymore. Closes #18451. Change-Id: I9a3b1190edbbe0ae3cedfe4df2993441d1f2d629 Reviewed-on: https://review.haiku-os.org/c/haiku/+/8975 Haiku-Format: Haiku-format Bot Tested-by: Commit checker robot Reviewed-by: waddlesplash --- src/system/libroot/os/locks/mutex.cpp | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/src/system/libroot/os/locks/mutex.cpp b/src/system/libroot/os/locks/mutex.cpp index 07a8f44d1c..4bcef54a72 100644 --- a/src/system/libroot/os/locks/mutex.cpp +++ b/src/system/libroot/os/locks/mutex.cpp @@ -90,12 +90,6 @@ __mutex_unlock(mutex *lock) _kern_mutex_unblock(&lock->lock, 0); } - if ((oldValue & B_USER_MUTEX_LOCKED) == 0) { -#if 0 + if ((oldValue & B_USER_MUTEX_LOCKED) == 0) debugger("mutex was not actually locked!"); -#else - // The above happens too often at present (see bug #18451). - _kern_debug_output("libroot __mutex_unlock: mutex was not actually locked!\n"); -#endif - } }