At times, you might find that running your code returns unintended results, yet does not cause a debugger to open on the error.

To diagnose the problem, you can add the message self halt to your code. When you next run your code, self halt interrupts execution and displays a debugger.

Using options in the debugger, you can then scan the message stack and see how each message affects objects defined by your code.