Hi Marcus,

On Mon, Dec 5, 2011 at 5:58 AM, Marcus Denker <marcus.den...@inria.fr>wrote:

> Hi,
>
> With this change set, we get an error when doing the following:
>
> In the workspace do a "debug it" on this code:
>
> Transcript show: Class name
>

Thanks very much for this simple test case :)  OK, the attached is an
improvement.  Please as many people test it as possible.


> then two times "step over" --> Subscript out of bounds error. Without
> the change it works.
>
> On Wed, Nov 16, 2011 at 8:58 PM, Eliot Miranda <eliot.mira...@gmail.com>
> wrote:
> > Hi All,
> >
> >     I've found a bug in ContextPart>>#runUntilErrorOrReturnFrom: that in
> a
> > certain rare circumstance causes the method to peel back too much of the
> > stack.  This method is used in the debugger (e.g. completeStep: et al)
> but
> > also in Process termination.  So it is right at the heart of the system.
> >  I'm loath to simply commit it  I'd really appreciate y'all testing with
> the
> > fix and reporting any changes you see.  It does not affect the trunk test
> > suite (there is a test, WeakSetInspectorTest, which is unreliable, but
> apart
> > form that no observed effects).  So, brave souls, please try with the
> > attached and see if you come to grief or not.
> > --
> > thanks,
> > Eliot
> >
>
>
>
> --
> --
> Marcus Denker  --  den...@acm.org
> http://www.marcusdenker.de
>
>


-- 
best,
Eliot

Attachment: ContextPart-runUntilErrorOrReturnFrom.st
Description: Binary data

Reply via email to