neobytes-project/neobytes
neobytes-project/neobytes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove -DDEBUG_LOCKORDER from debug configuration (#1010)

Browse Source 
* Remove -DDEBUG_LOCKORDER from debug configuration

* Updated documentation to reflect removal of -DDEBUG_LOCKORDER from debug configuration
This commit is contained in:
Tim Flynn 2016-09-12 03:40:23 -04:00 committed by UdjinM6
parent f5738c001f
commit e61b783e0e
2 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
configure.ac
View File

@ -171,7 +171,7 @@ AC_ARG_ENABLE([debug],
[enable_debug=no]) [enable_debug=no])
if test "x$enable_debug" = xyes; then if test "x$enable_debug" = xyes; then
CPPFLAGS="$CPPFLAGS -DDEBUG -DDEBUG_LOCKORDER" CPPFLAGS="$CPPFLAGS -DDEBUG"
if test "x$GCC" = xyes; then if test "x$GCC" = xyes; then
CFLAGS="$CFLAGS -g3 -O0" CFLAGS="$CFLAGS -g3 -O0"
fi fi

3
doc/developer-notes.md
View File

@ -329,8 +329,7 @@ Threads and synchronization
---------------------------- ----------------------------
- Build and run tests with `-DDEBUG_LOCKORDER` to verify that no potential - 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 deadlocks are introduced.
configuring with `--enable-debug`
- When using `LOCK`/`TRY_LOCK` be aware that the lock exists in the context of - 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 the current scope, so surround the statement and the code that needs the lock