June 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Debugger weirdness

by phil＠highoctane.be

On Tue, Jun 3, 2014 at 2:09 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 03 Jun 2014, at 08:52, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > > On 3 juin 2014, at 13:34, ClÃ©ment Bera <bera.clement(a)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(a)highoctane.be <phil(a)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 >> > > > >

June 3, 2014

Re: [Pharo-dev] Debugger weirdness

by ClÃ©ment Bera

2014-06-03 14:09 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 03 Jun 2014, at 08:52, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > > On 3 juin 2014, at 13:34, ClÃ©ment Bera <bera.clement(a)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 phil(a)highoctane.be <phil(a)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 >> > > > >

June 3, 2014

Re: [Pharo-dev] Debugger weirdness

by ClÃ©ment Bera

2014-06-03 13:52 GMT+02:00 Camille Teruel <camille.teruel(a)gmail.com>: > > On 3 juin 2014, at 13:34, ClÃ©ment Bera <bera.clement(a)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 was talking about this case: DebugContext>>blockNotFoundDialog: aMethod with: aText | browser message result | message := 'Method for block not found on stack, can''t edit and continue'. [ ... ] > Isn't that your case ? > > > 2014-06-03 13:13 GMT+02:00 phil(a)highoctane.be <phil(a)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 >> > > >

June 3, 2014

Re: [Pharo-dev] Debugger weirdness

by Esteban Lorenzano

On 03 Jun 2014, at 08:52, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > On 3 juin 2014, at 13:34, ClÃ©ment Bera <bera.clement(a)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 :( Esteban > >> >> Isn't that your case ? >> >> >> 2014-06-03 13:13 GMT+02:00 phil(a)highoctane.be <phil(a)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 >> >

June 3, 2014

Re: [Pharo-dev] Debugger weirdness

by Camille Teruel

On 3 juin 2014, at 13:34, ClÃ©ment Bera <bera.clement(a)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? > > Isn't that your case ? > > > 2014-06-03 13:13 GMT+02:00 phil(a)highoctane.be <phil(a)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 >

June 3, 2014

Re: [Pharo-dev] Debugger weirdness

by ClÃ©ment Bera

Hello, It happens sometimes when you edit a blockClosure code and that the debugger cannot find it on stack. Isn't that your case ? 2014-06-03 13:13 GMT+02:00 phil(a)highoctane.be <phil(a)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 >

June 3, 2014

Debugger weirdness

by 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

June 3, 2014

Re: [Pharo-dev] ConfigurationOfMorphicCore

by Pavel Krivanek

Thank you, Doru, the initial redrawing problems are quite common and I have no clue how to avoid them. Keyboard should do nothing. Cheers, -- Pavel 2014-06-03 12:34 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Very cool. I just tested it on Mac OS X 10.9.3 and I get a little blue box > that I can drag around. The background is at the beginning white and there > are blue artifacts leftover, but after I resize the window the background > gets green and there is no more blue artifacts left around. > > I did not manage to produce any effect with the keyboard. > > Cheers, > Doru > > > On Jun 3, 2014, at 12:07 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > > Hi, > > > > I created a job that bootstraps MorphicCore - an image that contains > runable subset of Morphic that is able only to display a simple morph and > handle mouse and keyboard events on it. Please, try to test the image on > Mac. > > > > > https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-3… > > > > Cheers, > > -- Pavel > > -- > www.tudorgirba.com > > "Speaking louder won't make the point worthier." > > >

June 3, 2014

Re: [Pharo-dev] ConfigurationOfMorphicCore

by Tudor Girba

Very cool. I just tested it on Mac OS X 10.9.3 and I get a little blue box that I can drag around. The background is at the beginning white and there are blue artifacts leftover, but after I resize the window the background gets green and there is no more blue artifacts left around. I did not manage to produce any effect with the keyboard. Cheers, Doru On Jun 3, 2014, at 12:07 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > I created a job that bootstraps MorphicCore - an image that contains runable subset of Morphic that is able only to display a simple morph and handle mouse and keyboard events on it. Please, try to test the image on Mac. > > https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-3… > > Cheers, > -- Pavel -- www.tudorgirba.com "Speaking louder won't make the point worthier."

June 3, 2014

ConfigurationOfMorphicCore

by Pavel Krivanek

Hi, I created a job that bootstraps MorphicCore - an image that contains runable subset of Morphic that is able only to display a simple morph and handle mouse and keyboard events on it. Please, try to test the image on Mac. https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo -4.0-Bootstrap-Step-3.0-ConfigurationOfMorphicCore/ Cheers, -- Pavel

June 3, 2014