Aha. Strange debugger behavior.
'asd' asd <do it>

Then when I enter the debugger, "proceed" on the notifier brings another
notifier.
Same thing if I press "debug", and then proceed with focus on the top
(error) context in the stack.
However, if I choose the DoIt context before pressing proceed, the error
is ignored, and evalution continues returning a nil.

Is this a feature or bug? 

Daniel

"David T. Lewis" <lewis at mail.msen.com> wrote:
> On Tue, Jun 10, 2003 at 10:08:01AM +0200, Daniel Vainsencher wrote:
> > "David T. Lewis" <lewis at mail.msen.com> wrote:
> > > Proceed through the debugger notifications, and you'll find that OSProcess
> > > and CommandShell work fine on Squeak 3.6alpha, and pass their SUnit tests.
> > > And of course if you load OSProcess into the 3.6 image with VM generation
> > > tools still in place, there is no problem at all.
> > Do you know a way to proceed through an MNU? 
> 
> Maybe I'm not using the same image you have, but here's what I did to
> reproduce your problem:
> 
> - Download ftp://st.cs.uiuc.edu/pub/Smalltalk/Squeak/3.6alpha/Squeak3.6a-5179.zip
> - Run the image from a VM (with the OSProcess plugin)
> - Load "OSProcess (3.0.4)" from SM (no problems)
> - Remove OSProcess
> - Load "VM generation removal (3)" from SM
> - Load "OSProcess (3.0.4)" from SM
>   -> get debugger with "MessageNotUnderstood: returnTypeC:"
> - Click "Proceed"
>   -> get debugger with "MessageNotUnderstood: varDeclareC:"
> - Click "Proceed"
>   -> get debugger with "MessageNotUnderstood: cCode:inSmalltalk:"
> - Click "Proceed"
>   -> get debugger with "MessageNotUnderstood: ="
> - Click "Proceed"
>   -> get debugger with "MessageNotUnderstood: mustBeBoolean"
> - Click "Proceed"
>   -> get debugger with "MessageNotUnderstood: returnTypeC:"
> - Click "Proceed"
> - Complete the installation
> - Run the sUnit tests (OK)
> - Load CommandShell from SM
> - Run the sUnit tests (OK)
> 
> Note: All the MNU errors are coming from OSProcessPlugin class>>about,
> which is called in the postscript of one of the change sets to display
> information about OSPP and the version numbers of the running plugin
> versus the version number of the code that just got loaded. This blows
> up because class OSProcessPlugin lost its brains as a result of not
> inheriting from InterpreterPlugin (which was removed from the system).
> 
> Dave