➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author izbyshev
Recipients benjamin.peterson, izbyshev, serhiy.storchaka, vstinner
Date 2018-11-09.22:33:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1541802807.41.0.788709270274.issue35204@psf.upfronthosting.co.za>
In-reply-to
Content 
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 function:

WARNING: ThreadSanitizer: heap-use-after-free (pid=24361)
  Read of size 4 at 0x7b7c00000020 by main thread:
    #0 address_in_range /scratch2/izbyshev/cpython/Objects/obmalloc.c:1312:23 (python+0x59e912)

==3515==WARNING: MemorySanitizer: use-of-uninitialized-value
    #0 0x9713f8 in address_in_range /scratch2/izbyshev/cpython/Objects/obmalloc.c:1313:35

I suggest to disable them for this function as well.
History
Date User Action Args
2018-11-09 22:33:27izbyshevsetrecipients: + izbyshev, vstinner, benjamin.peterson, serhiy.storchaka
2018-11-09 22:33:27izbyshevsetmessageid: <1541802807.41.0.788709270274.issue35204@psf.upfronthosting.co.za>
2018-11-09 22:33:27izbyshevlinkissue35204 messages
2018-11-09 22:33:27izbyshevcreate