STINNER Victor added the comment: 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. ---------- Added file: http://bugs.python.org/file42116/tracemalloc_track-2.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26530> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
