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 amaury.forgeotdarc, belopolsky, eric.snow, neologix, python-dev, rhettinger, tim.peters, vstinner
Date 2013-11-23.01:37:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385170651.36.0.169012028243.issue18874@psf.upfronthosting.co.za>
In-reply-to
Content
Oh, Jim Jewett found a bug: if set_traceback_limit() is called while tracemalloc is tracing, two tracebacks are seen different because their length is different, whereas the full traceback would be the same.

To avoid this issue, I propose to add an optional nframe parameter to the set_traceback_limit() function.

With this API, it may be possible to remove the arbitrary limitation of 100 frames by allocating a buffer in start().
History
Date User Action Args
2013-11-23 01:37:31vstinnersetrecipients: + vstinner, tim.peters, rhettinger, amaury.forgeotdarc, belopolsky, neologix, python-dev, eric.snow
2013-11-23 01:37:31vstinnersetmessageid: <1385170651.36.0.169012028243.issue18874@psf.upfronthosting.co.za>
2013-11-23 01:37:31vstinnerlinkissue18874 messages
2013-11-23 01:37:31vstinnercreate