The custom zone implementation for OS X must not return 0 (even for 0-sized allocations). Returning 0 indicates that the pointer doesn't belong to the zone. This can break existing applications. The underlaying allocator allocates 1 byte for 0-sized allocations anyway, so returning 1 in this case is okay.
Details
Details
- Reviewers
kcc glider dvyukov samsonov - Commits
- rG173c690a6182: [tsan] Fix size reporting for OS X zone allocator with 0-sized allocations
rCRT266283: [tsan] Fix size reporting for OS X zone allocator with 0-sized allocations
rL266283: [tsan] Fix size reporting for OS X zone allocator with 0-sized allocations
Diff Detail
Diff Detail