Message261507
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. |
|
Date |
User |
Action |
Args |
2016-03-10 16:07:57 | vstinner | set | recipients:
+ vstinner, pitrou, njs |
2016-03-10 16:07:56 | vstinner | set | messageid: <1457626076.89.0.677921944213.issue26530@psf.upfronthosting.co.za> |
2016-03-10 16:07:56 | vstinner | link | issue26530 messages |
2016-03-10 16:07:56 | vstinner | create | |
|