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 pitrou
Recipients njs, pitrou, python-dev, vstinner
Date 2016-09-01.14:03:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1472738581.46.0.466932596819.issue26530@psf.upfronthosting.co.za>
In-reply-to
Content
Which patch are we talking about? In tracemalloc_track-3.patch, I see:

+   If memory block is already tracked, update the existing trace. */
+PyAPI_FUNC(int) _PyTraceMalloc_Track(void *ptr, size_t size);
+
+/* Untrack an allocated memory block in the tracemalloc module.
+   Do nothing if the block was not tracked.
+
+   Do nothing if tracemalloc is not tracing Python memory allocations. */
+PyAPI_FUNC(void) _PyTraceMalloc_Untrack(void *ptr);
History
Date User Action Args
2016-09-01 14:03:01pitrousetrecipients: + pitrou, vstinner, njs, python-dev
2016-09-01 14:03:01pitrousetmessageid: <1472738581.46.0.466932596819.issue26530@psf.upfronthosting.co.za>
2016-09-01 14:03:01pitroulinkissue26530 messages
2016-09-01 14:03:01pitroucreate