apr-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 48535] Potential data race on allocator->max_index in allocator_alloc()
Date Fri, 29 Jan 2010 12:06:12 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=48535

--- Comment #2 from Bart Van Assche <bart.vanassche@gmail.com> 2010-01-29 04:06:11 UTC
---
(In reply to comment #1)
> Isn't this an intentional race condition, following the usual pattern
> 
> make a very cheap but imperfect state check
> if it looks good so far:
>   get mutex
>   check state carefully this time, handle appropriately
>   release mutex

I agree with the above. The reason that I filed this report is not because I
suspect a bug in APR but because the thread checker reports are annoying.
Thread checking tools (Intel Parallel Studio, Intel Thread Checker, DRD,
Helgrind, ...) complain about this construct during every run of every
application that uses the APR.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@apr.apache.org
For additional commands, e-mail: bugs-help@apr.apache.org


Mime
View raw message