From f966e5397ed8f5c42c185223fc9b4d750a678d02 Mon Sep 17 00:00:00 2001 From: Victor Stinner Date: Tue, 13 Nov 2018 15:14:58 +0100 Subject: bpo-29564:_PyMem_DumpTraceback() suggests enabling tracemalloc (GH-10510) If tracemalloc is not tracing Python memory allocations, _PyMem_DumpTraceback() now suggests to enable tracemalloc to get the traceback where the memory block has been allocated. --- Modules/_tracemalloc.c | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'Modules/_tracemalloc.c') diff --git a/Modules/_tracemalloc.c b/Modules/_tracemalloc.c index 1005f2ea4d..c5d5671032 100644 --- a/Modules/_tracemalloc.c +++ b/Modules/_tracemalloc.c @@ -1471,6 +1471,12 @@ _PyMem_DumpTraceback(int fd, const void *ptr) traceback_t *traceback; int i; + if (!_Py_tracemalloc_config.tracing) { + PUTS(fd, "Enable tracemalloc to get the memory block " + "allocation traceback\n\n"); + return; + } + traceback = tracemalloc_get_traceback(DEFAULT_DOMAIN, (uintptr_t)ptr); if (traceback == NULL) return; -- cgit v1.2.1