Yes this is super annoying because I get really confused
On Sat, May 13, 2017 at 11:10 PM, p...@highoctane.be
wrote:
> I also have to scroll up to see the last frame (Pharo 5.0).
>
> Phil
>
> On Sat, May 13, 2017 at 9:27 PM, Stephane Ducasse > wrote:
>
>> In fact my test was broken an in additi
I also have to scroll up to see the last frame (Pharo 5.0).
Phil
On Sat, May 13, 2017 at 9:27 PM, Stephane Ducasse
wrote:
> In fact my test was broken an in addition the debugger does not show the
> top frame and it took me a while to see that I
> should always scroll to be the stack.
> And I w
In fact my test was broken an in addition the debugger does not show the
top frame and it took me a while to see that I
should always scroll to be the stack.
And I was always only seeing this mustBeABoolean.
On Sat, May 13, 2017 at 9:17 PM, Tudor Girba wrote:
> Hi,
>
> I am not quite sure where
Hi,
I am not quite sure where the issue is because I cannot seem to reproduce the
problem.
I try this Playground script:
Object subclass: #ABC
instanceVariableNames: ''
classVariableNames: ''
package: 'ABC'.
ABC compile: 'doesNotUnderstand: aMessage
"support sen
Hi
In the past it was possible to step throw such code and now we cannot
anymore
because of a smart trick. I should say that I hate when we break the
reachibility and understandibility of the system.
So why I cannot get a debugger opens after the halt: ?
How do I get that ?
Now I will put traces:
