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 Mark.Shannon
Recipients Mark.Shannon
Date 2020-04-08.15:47:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1586360855.72.0.434652598832.issue40228@roundup.psfhosted.org>
In-reply-to
Content
Debuggers are allowed to change the line number of the currently executing frame. Regardless of whether this is sensible or not, the current implementation rather fragile.

The code makes various assumptions about the layout of the bytecode that may not be true in the future, and I suspect, are not true now.

We should use a more brute-force approach of computing the exception stack for the whole function and then searching for a safe place to jump to. This is not only more robust it allows more jumps.

For example, it is safe to jump from one exception handler to another.
It may not be sensible, but it is safe.
History
Date User Action Args
2020-04-08 15:47:35Mark.Shannonsetrecipients: + Mark.Shannon
2020-04-08 15:47:35Mark.Shannonsetmessageid: <1586360855.72.0.434652598832.issue40228@roundup.psfhosted.org>
2020-04-08 15:47:35Mark.Shannonlinkissue40228 messages
2020-04-08 15:47:35Mark.Shannoncreate