summaryrefslogtreecommitdiff
path: root/src/thread-utils.h
diff options
context:
space:
mode:
authorRussell Belfer <rb@github.com>2013-05-31 14:13:11 -0700
committerRussell Belfer <rb@github.com>2013-05-31 14:13:11 -0700
commit1a42dd17eb2c35fa572418f5958595cbe297d229 (patch)
treef135f3788eb20b5ac100519c41c7525f5f830457 /src/thread-utils.h
parentf658dc433cae351e72b1c8b245724eafb43f5844 (diff)
downloadlibgit2-1a42dd17eb2c35fa572418f5958595cbe297d229.tar.gz
Mutex init can fail
It is obviously quite a serious problem if this happens, but mutex initialization can fail and we should detect it. It's a bit like a memory allocation failure, in that you're probably pretty screwed if this occurs, but at least we'll catch it.
Diffstat (limited to 'src/thread-utils.h')
-rw-r--r--src/thread-utils.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/thread-utils.h b/src/thread-utils.h
index 49b5f3b5e..d4ed7e73b 100644
--- a/src/thread-utils.h
+++ b/src/thread-utils.h
@@ -140,7 +140,7 @@ GIT_INLINE(int64_t) git_atomic64_add(git_atomic64 *a, int64_t addend)
/* Pthreads Mutex */
#define git_mutex unsigned int
-#define git_mutex_init(a) (void)0
+#define git_mutex_init(a) 0
#define git_mutex_lock(a) 0
#define git_mutex_unlock(a) (void)0
#define git_mutex_free(a) (void)0