From: Johannes Schindelin Date: Tue, 25 Oct 2011 17:25:20 +0000 (-0500) Subject: git grep: be careful to use mutexes only when they are initialized X-Git-Tag: v1.7.8-rc0~5^2~2 X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=cdf055376907cfa7837e576db219a1a7617df276;p=git.git git grep: be careful to use mutexes only when they are initialized Rather nasty things happen when a mutex is not initialized but locked nevertheless. Now, when we're not running in a threaded manner, the mutex is not initialized, which is correct. But then we went and used the mutex anyway, which -- at least on Windows -- leads to a hard crash (ordinarily it would be called a segmentation fault, but in Windows speak it is an access violation). This problem was identified by our faithful tests when run in the msysGit environment. To avoid having to wrap the line due to the 80 column limit, we use the name "WHEN_THREADED" instead of "IF_USE_THREADS" because it is one character shorter. Which is all we need in this case. Signed-off-by: Johannes Schindelin Signed-off-by: Junio C Hamano --- diff --git a/builtin/grep.c b/builtin/grep.c index 7d0779f6c..88b0c8013 100644 --- a/builtin/grep.c +++ b/builtin/grep.c @@ -77,10 +77,11 @@ static pthread_mutex_t grep_mutex; /* Used to serialize calls to read_sha1_file. */ static pthread_mutex_t read_sha1_mutex; -#define grep_lock() pthread_mutex_lock(&grep_mutex) -#define grep_unlock() pthread_mutex_unlock(&grep_mutex) -#define read_sha1_lock() pthread_mutex_lock(&read_sha1_mutex) -#define read_sha1_unlock() pthread_mutex_unlock(&read_sha1_mutex) +#define WHEN_THREADED(x) do { if (use_threads) (x); } while (0) +#define grep_lock() WHEN_THREADED(pthread_mutex_lock(&grep_mutex)) +#define grep_unlock() WHEN_THREADED(pthread_mutex_unlock(&grep_mutex)) +#define read_sha1_lock() WHEN_THREADED(pthread_mutex_lock(&read_sha1_mutex)) +#define read_sha1_unlock() WHEN_THREADED(pthread_mutex_unlock(&read_sha1_mutex)) /* Signalled when a new work_item is added to todo. */ static pthread_cond_t cond_add;