BIND 10 #2198: make sure InterprocessSyncLocker is thread safe
BIND 10 Development
do-not-reply at isc.org
Thu Oct 18 06:58:03 UTC 2012
#2198: make sure InterprocessSyncLocker is thread safe
-------------------------------------+-------------------------------------
Reporter: | Owner: vorner
jinmei | Status: reviewing
Type: | Milestone:
defect | Sprint-20121023
Priority: | Resolution:
medium | Sensitive: 0
Component: | Sub-Project: Core
logging | Estimated Difficulty: 5
Keywords: | Total Hours: 3.25
Defect Severity: N/A |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by muks):
* owner: muks => vorner
* status: reopened => reviewing
Comment:
Up for review. The changes for the above issues should be self-
explanatory.
* On Mac OS, one more change was made to make it look in the `builddir`
for libb10-threads library.
* Two objects are left created (leaked) in InterprocessSyncFile to avoid
the static destruction fiasco. This is not a leak worth bothering though
as it doesn't grow with time. With some clever arrangement of
instantiation, we can avoid the static destruction fiasco, but I think the
approach in the branch is safer.
--
Ticket URL: <http://bind10.isc.org/ticket/2198#comment:25>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list