haha, well, if any of you can provide a way to reproduce the problem, I will take a look.
2014-06-03 14:46 GMT+02:00 Clément Bera <bera.clem...@gmail.com>: > > 2014-06-03 14:09 GMT+02:00 Esteban Lorenzano <esteba...@gmail.com>: > > >> On 03 Jun 2014, at 08:52, Camille Teruel <camille.ter...@gmail.com> >> wrote: >> >> >> On 3 juin 2014, at 13:34, Clément Bera <bera.clem...@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 :( >> > > Yeah I also had the problem ... > > Fortunately, one of the debugger implementor (that I will not name here) > is working in our team right now and she may be able to fix it :-) > > >> >> Esteban >> >> >> >> Isn't that your case ? >> >> >> 2014-06-03 13:13 GMT+02:00 p...@highoctane.be <p...@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 >>> >> >> >> >> >
