From e61b783e0e7416034dd4d802ec5e05205b3dde67 Mon Sep 17 00:00:00 2001 From: Tim Flynn Date: Mon, 12 Sep 2016 03:40:23 -0400 Subject: [PATCH] Remove -DDEBUG_LOCKORDER from debug configuration (#1010) * Remove -DDEBUG_LOCKORDER from debug configuration * Updated documentation to reflect removal of -DDEBUG_LOCKORDER from debug configuration --- configure.ac | 2 +- doc/developer-notes.md | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/configure.ac b/configure.ac index 56214e906..c6e9db0cd 100644 --- a/configure.ac +++ b/configure.ac @@ -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 diff --git a/doc/developer-notes.md b/doc/developer-notes.md index c6945ea38..62a4e35d6 100644 --- a/doc/developer-notes.md +++ b/doc/developer-notes.md @@ -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