➜

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 vstinner
Recipients jd, vstinner
Date 2019-08-29.17:41:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1567100505.24.0.0612014756042.issue37961@roundup.psfhosted.org>
In-reply-to
Content 
> However, if the number of frames is truncated, there's no way to know the original length of the stack traces.

PR 15545 makes each trace 4 bytes (sizeof int) larger. Would it be enough for you to only know if the traceback is truncated?

tracemalloc is already "memory heavy", so I don't think that making trace_t larger is a blocker issue :-)
History
Date User Action Args
2019-08-29 17:41:45vstinnersetrecipients: + vstinner, jd
2019-08-29 17:41:45vstinnersetmessageid: <1567100505.24.0.0612014756042.issue37961@roundup.psfhosted.org>
2019-08-29 17:41:45vstinnerlinkissue37961 messages
2019-08-29 17:41:44vstinnercreate