On Tue, Jun 3, 2014 at 2:09 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 03 Jun 2014, at 08:52, Camille Teruel <camille.teruel@gmail.com> wrote:
On 3 juin 2014, at 13:34, Clément Bera <bera.clement@gmail.com> wrote:
Hello,
It happens sometimes when you edit a blockClosure code and that the debugger cannot find it on stack.
Why would the debugger need to find a context for an edited block? The only reason I see would be on-stack replacement, but AFAIK the debugger doesn't do that, does it?
I have spotted this problem too, outside block closures. It is not every time but it happens occasionally. I think is some sort of bug :(
I takes away a lot of the fun... Especially when my image gets locked, no matter how much I hit the interrupt key sequence. 'Through', 'Over', 'Restart', ... it is not working nicely. Is that because of the new debugger/compiler chain? Phil
Esteban
Isn't that your case ?
2014-06-03 13:13 GMT+02:00 phil@highoctane.be <phil@highoctane.be>:
While debugging, I modify the code of the method, then accept, then restart.
But when going back to the method in the browser, it is unchanged.
What I am doing wrong or is this something other people do encounter?
I didn't had this in 2.0
Phil