Remove -DDEBUG_LOCKORDER from debug configuration (#1010)
* Remove -DDEBUG_LOCKORDER from debug configuration * Updated documentation to reflect removal of -DDEBUG_LOCKORDER from debug configuration
This commit is contained in:
parent
f5738c001f
commit
e61b783e0e
@ -171,7 +171,7 @@ AC_ARG_ENABLE([debug],
|
||||
[enable_debug=no])
|
||||
|
||||
if test "x$enable_debug" = xyes; then
|
||||
CPPFLAGS="$CPPFLAGS -DDEBUG -DDEBUG_LOCKORDER"
|
||||
CPPFLAGS="$CPPFLAGS -DDEBUG"
|
||||
if test "x$GCC" = xyes; then
|
||||
CFLAGS="$CFLAGS -g3 -O0"
|
||||
fi
|
||||
|
@ -329,8 +329,7 @@ Threads and synchronization
|
||||
----------------------------
|
||||
|
||||
- Build and run tests with `-DDEBUG_LOCKORDER` to verify that no potential
|
||||
deadlocks are introduced. As of 0.12, this is defined by default when
|
||||
configuring with `--enable-debug`
|
||||
deadlocks are introduced.
|
||||
|
||||
- When using `LOCK`/`TRY_LOCK` be aware that the lock exists in the context of
|
||||
the current scope, so surround the statement and the code that needs the lock
|
||||
|
Loading…
Reference in New Issue
Block a user