Just noticed that the second bug also appears in the new debugger. To reproduce execute (with either debugger) while debugging add a message send to a method that does not exist, step into that message send and then choose to create the method. After you created you'll get: UndefinedObject(Object)>> doesNotUnderstand: #debugHighlightRange Andrei On Mon, Jul 15, 2013 at 9:37 AM, Clément Bera <bera.clement@gmail.com>wrote:
Hi,
Actually I saw the bug, tried in the new debugger, it worked. So I didn't fix it because the new debugger will be integrated before the release.
2013/7/14 Andrei Vasile Chis <chisvasileandrei@gmail.com>
Hi,
Executing '1 haba' in a workspace and then choosing create method from the pre debug window leads to this exception: UndefinedObject(Object)>>doesNotUnderstand: #methodOrBlockNode
If instead I choose to debug, select the top context of the stack and the press the 'Creare method' button a different exception is thrown: UndefinedObject(Object)>>doesNotUnderstand: #debugHighlightRange
In both cases the method is created.
So known or unknown issue? Also it doesn't seem to happen with the new debugger. Not sure why :)
Andrei