This is the scenario:

• a ruby script runs with the macro IDE open
• "Ask whether to stop in debugger on exception" is enabled in the debugger options
• an exception is raised inside some function which itself is called from another function

Effect: the IDE shows the exception and offers to stop on that exception. If this is declined, the exception will be propagated upwards in the call chain. Every time, the exception is raised on the next level in the call chain, the IDE will again offer to stop. This becomes tedious if many levels are involved.