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 Sun, 31 Jan 2010 17:38:46 GMT

--- Comment #4 from Bart Van Assche <bart.vanassche@gmail.com> 2010-01-31 09:38:46 UTC
(In reply to comment #3)
> Is there a -DPURIFY-like constant that is in standard use, which could be used
> to ifdef-munge the code, to avoid the lazy check?  Given that the code is valid
> it would be better to fix the analysis tools to be smarter than to make the
> code dumber.

Recent DRD and Helgrind versions support annotations like
these annotations are not supported by thread checking tools on Windows.

An approach that might work with all four mentioned data race detectors is to
replace the read of allocator->index outside the critical section by an atomic
read. Doing so would suppress race reports.

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

View raw message