Fix several places where an exception could be chained wrongly #7566
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If an exception's chain or context can refer to a pointer from a different VM, a crash would typically result.
This couldn't turn up on UNIX testing because the VM is never torn down and rebuilt like it is on hardware.
Testing performed: Ran the original reproducer on a Feather RP2040 Scorpio and verified the reported behavior. Ran with the fix and it no longer reproduced.
While I think that WatchdogException could have led to similar behavior, and made fixes for this, I didn't test it. I did verify scenarios with KeyboardInterrupt and ReloadException are fixed.
Closes: #7565