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 scoder
Recipients nedbat, scoder, serhiy.storchaka, vstinner
Date 2018-07-08.07:07:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1531033635.0.0.56676864532.issue34068@psf.upfronthosting.co.za>
In-reply-to
Content
I added this assertion exactly for the purpose of finding this kind of bug. It means that some code tried to look up an attribute with a live exception set, which previously could swallow the exception in certain situations, and even if not, it is always the wrong thing to do.

Looking at the stack trace, my guess is that the problem is closer to the crash than the coverage calls. I'd suggest taking a look at the frame cleanup in the traceback module.
History
Date User Action Args
2018-07-08 07:07:15scodersetrecipients: + scoder, vstinner, nedbat, serhiy.storchaka
2018-07-08 07:07:15scodersetmessageid: <1531033635.0.0.56676864532.issue34068@psf.upfronthosting.co.za>
2018-07-08 07:07:14scoderlinkissue34068 messages
2018-07-08 07:07:14scodercreate