Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(65)

Issue 6038: Enable error checking on Posix locks in debug, and make release lock creation... (Closed)

Created:
12 years, 2 months ago by Dean McNamee
Modified:
9 years, 7 months ago
Reviewers:
Mark Mentovai, mendola
CC:
chromium-reviews_googlegroups.com
Visibility:
Public.

Description

Enable error checking on Posix locks in debug, and make release lock creation do a little bit less work. Based on suggestions by Gaetano Mendola.

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+7 lines, -1 line) Patch
M base/lock_impl_posix.cc View 1 chunk +7 lines, -1 line 1 comment Download

Messages

Total messages: 3 (0 generated)
Dean McNamee
12 years, 2 months ago (2008-10-01 13:49:47 UTC) #1
Mark Mentovai
LGTM? Did you check in the "explicit" thing separately?
12 years, 2 months ago (2008-10-01 14:03:52 UTC) #2
mendola
12 years, 2 months ago (2008-10-01 14:25:21 UTC) #3
Added comment

http://codereview.chromium.org/6038/diff/1/2
File base/lock_impl_posix.cc (right):

http://codereview.chromium.org/6038/diff/1/2#newcode26
Line 26: #endif
this is fine if we want an undefined behavior in case of a relock instead of
deadlock, in case we prefer the deadlock then the mutex shall be initialized
with PTHREAD_MUTEX_NORMAL instead of PTHREAD_MUTEX_DEFAULT as it is now.

Powered by Google App Engine
This is Rietveld 408576698