i2p/haiku-beta6
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

libroot/os: Re-enable "was not actually locked!" assertion.

Browse Source 
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 <[email protected]>
Tested-by: Commit checker robot <[email protected]>
Reviewed-by: waddlesplash <[email protected]>
This commit is contained in:
Augustin Cavalier
2025-02-13 22:43:57 +00:00
committed by waddlesplash
parent 9cd1e917ef
commit 19f1423287
1 changed files with 1 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/system/libroot/os/locks/mutex.cpp
+1 -7
View File
@@ -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
}
}