Morph debugging tips / tricks?
mdr at scn.org
Sun Oct 8 08:20:46 UTC 2000
Henrik Gedenryd <Henrik.Gedenryd at lucs.lu.se> wrote:
> Mike Rutenberg wrote:
> > With MVC I can press interrupt to see what is executing at a given time,
> > and don't see a dynamic equivalent in Morphic. How do people handle
> > this, if at all?
> That ought to work in Morphic as well. However, cmd-dot has been in limbo
> with the new event stuff, although that should be fixed in the current vm.
I was probably not clear enough.
In the old MVC, you could typically INTERRUPT a running operation, and
the core processing loop of what you were doing would be available
directly in the debugger. For example, the classic Dan demo of
interrupting a text selection activity, exploring the code, changing it
to do highlighting differently and continuing.
I reported a text selection bug a few days ago. I can not interrupt the
running code in the same way to see what is going on. I have to instead
make an educated guess, add breakpoints, and see if it traps to the
Morphic feels significantly more dynamic to me in my role as a "user"
but more static (and similar to traditional C environments) in my role
as (MVC aware) Squeaker. I am not sure if I am just misunderstanding
how to use it, or that it it actually missing that.
> My favorite is to use the Event Recorder to record and replay a problematic
> behavior, so that bugs in event-related code don't mess up the rest of the
> programming environment. (Eg. failure to drop a morph from the hand--try
> recovering from that!)
Neat, and thanks!
More information about the Squeak-dev