On 3 June 2014 13:46, Clément Bera <[email protected]> wrote: > > 2014-06-03 14:09 GMT+02:00 Esteban Lorenzano <[email protected]>: > >> >> On 03 Jun 2014, at 08:52, Camille Teruel <[email protected]> wrote: >> >> >> On 3 juin 2014, at 13:34, Clément Bera <[email protected]> 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 :-)
I started implementing this for Squeak, and then got snowed under by Real Life :( Had that not happened, you might have been able to spare some cycles. Sorry! frank >> Esteban >> >> >> >> Isn't that your case ? >> >> >> 2014-06-03 13:13 GMT+02:00 [email protected] <[email protected]>: >>> >>> 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
