Sorry about that; can we get a test case for this?
Does this one persist with 2295 or later, which has our reworked debug infrastructure?
Good Q. can you reproduce the same behavior in Water (which uses the parts of the newer debug infrastructure, even before 2295 and — more importantly — would allow us to do some better diagnosing on where the debugger gets stuck/caught on)?