Hi Eliot,

I'm very sorry for this bug, which was so unnecessary because my image has still a gigantic working copy ...! Tools-ct.988 should fix the issue, I tested it in a fresh trunk image. But it would be probably better if you could test it yourself, too. ;-)

Best,

Christoph

PS: #stepToStatement gets relevant with the BytecodeDebugger changeset I proposed somewhen earlier in this year. I still would appreciate any review of it! :-)

Von: Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von Eliot Miranda <eliot.miranda@gmail.com>
Gesendet: Donnerstag, 24. September 2020 21:42:37
An: The general-purpose Squeak developers list
Betreff: Re: [squeak-dev] tedious programming-in-the-debugger error needs fixing

Hi Christoph,

I didn't do my due dilligence in reviewing the changes. I've just hit a problem. When I accept as method in the debugger I get an MNU of stepToStatement. MorphicDebugger needs to implement stepToStatement, or contents:notifying: needs not to send it. Can you please fix ASAP? Apologies!!

On Thu, Sep 3, 2020 at 5:50 AM Christoph Thiede <christoph.thiede@student.hpi.uni-potsdam.de> wrote:

Hi Eliot,

when you reported this issue, I was not able to reproduce it. About two
months later, your new Sista bytecode set has arrived in the Trunk. Today, I
encountered a very similar issue, could reproduce it, and trace it back to a
comparison issue of Context >> #method which was affected by the
introduction of CompiledBlock instances. Is it possible that you already
used Sista in your image when reporting this bug?

In case you were able to reproduce the bug: Can you confirm whether
Tools-ct.987 (inbox) fixes the issue for you? :-)

Best,
Christoph

--
Sent from: http://forum.world.st/Squeak-Dev-f45488.html

_,,,^..^,,,_

best, Eliot