Re: BUG/REGRESSION while debugging Generator >> #nextPut:
Posted by
Eliot Miranda-2 on
Dec 15, 2019; 9:55pm
URL: https://forum.world.st/BUG-REGRESSION-while-debugging-Generator-nextPut-tp5108125p5108205.html
Hi David, Hi Christoph,
On Sun, Dec 15, 2019 at 8:52 AM David T. Lewis <
[hidden email]> wrote:
On Sat, Dec 14, 2019 at 04:09:22PM -0800, Eliot Miranda wrote:
>
>
> > On Dec 14, 2019, at 5:43 AM, Thiede, Christoph <[hidden email]> wrote:
> >
> > ???
> > By request, screenshots from a clean image ...
> >
> >
> > <pastedImage.png>
> >
> > ??? Press over
> >
> > Press cmd-dot ???
> >
> > <pastedImage.png>
> >
> >
> >
> >
> > The screenshots from 5.1 were made in a clean 5.1 image.
> >
>
> Hi Christoph,
>
> I???ve tried this in two trunk 64-bit images, one with the V3PlusClosures bytecode set and one with the SistaV1 bytecode set and no problem occurs in either case. If this only happens in a clean 5.1 image then I suspect it has already been fixed.
>
I can reproduce the problem in my trunk image. Chrostoph's example
is to debug this:
Generator on: [:stream | stream nextPut: #foo]
The failure happens when I step over the #nextPut:
If I step into the #nextPut: then all is well.
Interesting. I indeed do step over (/not/ step into) and do /not/ see the bug. Dave, Christoph, what VMs are you running?