Stability of Squeak

Andrew C. Greenberg werdna at mucow.com
Tue Aug 14 16:33:14 UTC 2001


It's always helpful to put together a changeset with the particular code 
you find crashing, or if you have a doIt that exemplifies the bug, just 
post it or a few methods in the e-mail.

> From: david at aminal.com
> Date: Tue Aug 14, 2001  12:31:33 PM US/Eastern
> To: squeak-dev at lists.squeakfoundation.org
> Subject: Re: Stability of Squeak
> Reply-To: squeak-dev at lists.squeakfoundation.org
>
> On Tue, Aug 14, 2001 at 09:21:37AM -0400, Mark Guzdial wrote:
>> Here at Georgia Tech, Squeak has a (relatively undeserved) reputation
>> for being prone to crashes.  The cause, for the most part, is due to
>> issues outside the software itself:
>
> Like newbies trying to trace through code they don't understand :-)
>
> You may remember, but I was asking questions about simulators, and you
> kindly provided some great info about the examples in the blue book.
>
> Well, I was trying to follow the code, and noticed that since a 
> DoNothing
> object seems to run in its own process, I couldn't see its interactions
> with the simulator by using the debugger. I had used a self halt in the
> demo class method to bring up a notify window, and then used the 
> debugger
> to step through the code. Even figured out that I had to use the 'send'
> button to trace method execution in other objects. So far, so good.




More information about the Squeak-dev mailing list