René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Error handling for some instructions is incorrect","articleBody":"In several places, we have `goto error;` branches in bytecode instructions that occur *after* modifying the `next_instr` pointer. This is incorrect, since the error branch will behave as if the error occurred in the *new* location (most often an adjacent instruction). The result could be as benign as an incorrect location in a traceback, or as problematic as incorrect control flow in or near a `try`/`except` block.\r\n\r\nI tried for a bit to make the compiler emit code that did the wrong thing here, and I wasn't able to. So this is mostly a theoretical concern (but still worth fixing).\n\n\u003c!-- gh-pr-number: gh-99299 --\u003e\n* PR: gh-99299\n\u003c!-- /gh-pr-number --\u003e\n\n\n\u003c!-- gh-pr-number: gh-99343 --\u003e\n* PR: gh-99343\n\u003c!-- /gh-pr-number --\u003e\n\n\n\u003c!-- gh-pr-number: gh-99398 --\u003e\n* PR: gh-99398\n\u003c!-- /gh-pr-number --\u003e\n","author":{"url":"https://github.com/brandtbucher","@type":"Person","name":"brandtbucher"},"datePublished":"2022-11-09T20:07:12.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/99298/cpython/issues/99298"}