Debugger bug ?

I'm not sure what's going on here, and maybe it's just something that isn't
supposed to work.  Still:

In a workspace:

    Cursor wait showWhile: [self halt].

Don't "debugIt", just evaluate it and enter the debugger from the walkback
dialog.

F11 five times.

Then as the debugger steps across the evaluation of:

    terminationBlock value.

in BlockClosure>>ensure:, the cursor changes to a wait cursor.  If you keep on
F11-ing, then the debugger will step right out of the evaluation leaving the
cursor "stuck" at wait.

(There's probably an easy way to reset it again, but I just quit my image
without saving).

    -- chris

Chris Uppal wrote:

> I'm not sure what's going on here, and maybe it's just something that isn't
> supposed to work.
> [snip]
>
> ... leaving the cursor "stuck" at wait.
>
> (There's probably an easy way to reset it again, but I just quit my image
> without saving).

I too have sometimes gotten myself with a "stuck" hourglass cursor after some
machinations in the debugger. I came up with the following in order to set it
back:

    [Processor sleep: 10. Cursor arrow makeCurrent] fork

Regards,
-Bill

-------------------------------------------
Bill Dargel            [hidden email]
Shoshana Technologies
100 West Joy Road, Ann Arbor, MI 48105  USA

Stepping through with SUnitBrowser seems to do it too - I was planning on
looking in to it -

jlo

"Bill Dargel" <[hidden email]> wrote in message
news:[hidden email]...
> Chris Uppal wrote:
>
> > I'm not sure what's going on here, and maybe it's just something that
isn't
> > supposed to work.
> > [snip]
> >
> > ... leaving the cursor "stuck" at wait.
> >
> > (There's probably an easy way to reset it again, but I just quit my
image
> > without saving).
>
> I too have sometimes gotten myself with a "stuck" hourglass cursor after
some
> machinations in the debugger. I came up with the following in order to set
it