When using the interactive debugger to browse a method that has been replaced by another method during packaging, the debugger will display the source for the original method, not the replacement method. Using the interactive debugger, methods can be changed during runtime processing.

Once the interactive debugger is active, changing and saving method source code within the debugger window causes the following to occur:

When the communication connection is made between the workstation and the target system, interaction with the image running on the target system is the same as for workstation Smalltalk development. For example, you can add breakpoints to your code as you would in a development image. Also, you can inspect and manipulate objects from the target system using Smalltalk expressions. The only difference is that you cannot save the runtime image as a resource on the target system, which means that before the next image invocation, you must re-package and re-install method changes on the target system.

You cannot create or change classes while in the interactive debugger.