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 14:05:45 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=48535

--- Comment #3 from Joe Orton <jorton@redhat.com> 2010-01-31 06:05:44 UTC ---
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.

-- 
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