[issue35204] Disable thread and memory sanitizers for address_in_range()

miss-islington added the comment: New changeset eff1c983eb0cc9bc01e8eba07a42522cee57 by Miss Islington (bot) in branch '3.6': closes bpo-35204: Disable thread and memory sanitizers for address_in_range(). (GH-10442)

[issue35204] Disable thread and memory sanitizers for address_in_range()

miss-islington added the comment: New changeset 1ec5781a097f4d4d988e0dd7f51ee203dc639df2 by Miss Islington (bot) in branch '3.7': closes bpo-35204: Disable thread and memory sanitizers for address_in_range(). (GH-10442)

[issue35204] Disable thread and memory sanitizers for address_in_range()

Change by miss-islington : -- pull_requests: +9741 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35204] Disable thread and memory sanitizers for address_in_range()

Benjamin Peterson added the comment: New changeset fd3a91cbf93dd7bd97f01add9c90075d63cd7316 by Benjamin Peterson (Alexey Izbyshev) in branch 'master': closes bpo-35204: Disable thread and memory sanitizers for address_in_range(). (GH-10442)

[issue35204] Disable thread and memory sanitizers for address_in_range()

Change by miss-islington : -- pull_requests: +9742 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35204] Disable thread and memory sanitizers for address_in_range()

Alexey Izbyshev added the comment: I've submitted a PR which implements the change with additional cleanups. GCC introduced TSan together with ASan in 4.8[1], but didn't provide a macro to test for -fsanitize=thread option until 7[2,3]. [1] https://gcc.gnu.org/gcc-4.8/changes.html [2]

[issue35204] Disable thread and memory sanitizers for address_in_range()

Change by Alexey Izbyshev : -- keywords: +patch pull_requests: +9714 stage: -> patch review ___ Python tracker ___ ___

[issue35204] Disable thread and memory sanitizers for address_in_range()

New submission from Alexey Izbyshev : address_in_range() in Objects/obmalloc.c may access memory that is mapped but is considered free by the underlying libc allocator. In #18596, address sanitizing was disabled for this function. But thread and memory sanitizers similarly trip on this