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 vstinner
Recipients njs, pitrou, vstinner
Date 2016-03-18.10:35:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1458297338.01.0.0450328155143.issue26530@psf.upfronthosting.co.za>
In-reply-to
Content
> So you guarantee tracemalloc itself won't use such a hack for other
purposes? ;-)

As the defacto maintainer of the module, yes, I can guarantee that.

> FWIW, LLVM calls the "domain" "address space", and simply uses an
> integer for it (0 being the default CPU-addressable address space).  You
> can probably restrict yourself to 8-bit address spaces...

I understood that we have the CPU and GPU address spaces. Do you know other address spaces?

I only care of address spaces where two equal pointers point to two different memory blocks.
History
Date User Action Args
2016-03-18 10:35:38vstinnersetrecipients: + vstinner, pitrou, njs
2016-03-18 10:35:38vstinnersetmessageid: <1458297338.01.0.0450328155143.issue26530@psf.upfronthosting.co.za>
2016-03-18 10:35:37vstinnerlinkissue26530 messages
2016-03-18 10:35:37vstinnercreate