Author vstinner
Recipients njs, pitrou, vstinner
Date 2016-03-10.16:07:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1457626076.89.0.677921944213.issue26530@psf.upfronthosting.co.za>
In-reply-to
Content
Antoine Pitrou:
> This may indeed be useful but:
> - those functions should be no-ops when tracing isn't enabled (so as to be as fast as possible)

Done

> - you should take the GIL if necessary (but only if tracing is enabled, of course)

Ok, done.

The new patch has a safer API:

* _PyTraceMalloc_Track() can be called twice with the same pointer: the old trace is removed, a new trace is added
* _PyTraceMalloc_Track() ensures that the GIL is hold
* _PyTraceMalloc_Track() & _PyTraceMalloc_Untrack() do nothing if tracemalloc is disabled

I also added unit tests.
History
Date User Action Args
2016-03-10 16:07:57vstinnersetrecipients: + vstinner, pitrou, njs
2016-03-10 16:07:56vstinnersetmessageid: <1457626076.89.0.677921944213.issue26530@psf.upfronthosting.co.za>
2016-03-10 16:07:56vstinnerlinkissue26530 messages
2016-03-10 16:07:56vstinnercreate