Re: [Pharo-project] Old bugs fixed by Opal
> Did you use https://ci.inria.fr/rmod/job/Opal/ The Opal in the image is a bit out-dated… >>> >>> I did just now, but there, debugging *anything* (even 3 + 4, or using cmd >>> dot) with the Opal Compiler set to default seemed to bring the image into a >>> near catatonic state… >>> Sort of hard to check if the buttons were fixed, with no debugger ever >>> opening. ;) >>> >> >> Yes, we committed some changes that might have broken things… >> I will check. >> > Ok, found it… at least the debugger appears again after a "self halt" :-) > > https://ci.inria.fr/rmod/job/Opal/lastSuccessfulBuild/artifact/Opal.zip > > We should remember to never think it works before the regression tester is > successful… > Clement wrote a blog post: > http://clementbera.wordpress.com/2013/03/22/toward-a-zero-bugs-interpreter-compiler/ nicely written :) Thanks clement this is cool! Push we are getting there.
Re: [Pharo-project] Old bugs fixed by Opal
On Apr 19, 2013, at 4:31 PM, Henrik Johansen wrote: > > On Apr 19, 2013, at 2:27 PM, Marcus Denker wrote: > >> >> On Apr 19, 2013, at 1:56 PM, Marcus Denker wrote: >> >>> >>> On Apr 19, 2013, at 1:35 PM, Henrik Johansen >>> wrote: >> > > Did you use > > https://ci.inria.fr/rmod/job/Opal/ > > The Opal in the image is a bit out-dated… I did just now, but there, debugging *anything* (even 3 + 4, or using cmd dot) with the Opal Compiler set to default seemed to bring the image into a near catatonic state… Sort of hard to check if the buttons were fixed, with no debugger ever opening. ;) >>> >>> Yes, we committed some changes that might have broken things… >>> I will check. >>> >> Ok, found it… at least the debugger appears again after a "self halt" :-) >> >> https://ci.inria.fr/rmod/job/Opal/lastSuccessfulBuild/artifact/Opal.zip >> >> We should remember to never think it works before the regression tester is >> successful… >> Clement wrote a blog post: >> http://clementbera.wordpress.com/2013/03/22/toward-a-zero-bugs-interpreter-compiler/ >> >> Marcus >> >> > That's *really* great! > With everything properly initialized, it works smoothly! (other than having > to click more than once to advance PC into the optimized to:do: blocks) > > One thing I ran into that doesn't work as I'd expect now, is UHE's when using > "Through"; > > Debugging > "nil asInteger" or, "ClosureTests new testToDoOutsideTemp" (which has > collection uninitialized, and exhibits the same at #add: send) > - pressing "Over" I get the expected behavior of opening > MessageNotUnderstood: in the same Debugger > - pressing "Through", I get the MNU in new pre-debugger after a lng delay > on first click, then, presumably with PC erroneously incremented, an > unrelated error on 2nd click, also in new pre-debugger. > Ok, we will have a look at that. Marcus
Re: [Pharo-project] Old bugs fixed by Opal
On Apr 19, 2013, at 2:27 PM, Marcus Denker wrote: > > On Apr 19, 2013, at 1:56 PM, Marcus Denker wrote: > >> >> On Apr 19, 2013, at 1:35 PM, Henrik Johansen >> wrote: > Did you use https://ci.inria.fr/rmod/job/Opal/ The Opal in the image is a bit out-dated… >>> >>> I did just now, but there, debugging *anything* (even 3 + 4, or using cmd >>> dot) with the Opal Compiler set to default seemed to bring the image into a >>> near catatonic state… >>> Sort of hard to check if the buttons were fixed, with no debugger ever >>> opening. ;) >>> >> >> Yes, we committed some changes that might have broken things… >> I will check. >> > Ok, found it… at least the debugger appears again after a "self halt" :-) > > https://ci.inria.fr/rmod/job/Opal/lastSuccessfulBuild/artifact/Opal.zip > > We should remember to never think it works before the regression tester is > successful… > Clement wrote a blog post: > http://clementbera.wordpress.com/2013/03/22/toward-a-zero-bugs-interpreter-compiler/ > > Marcus > > That's *really* great! With everything properly initialized, it works smoothly! (other than having to click more than once to advance PC into the optimized to:do: blocks) One thing I ran into that doesn't work as I'd expect now, is UHE's when using "Through"; Debugging "nil asInteger" or, "ClosureTests new testToDoOutsideTemp" (which has collection uninitialized, and exhibits the same at #add: send) - pressing "Over" I get the expected behavior of opening MessageNotUnderstood: in the same Debugger - pressing "Through", I get the MNU in new pre-debugger after a lng delay on first click, then, presumably with PC erroneously incremented, an unrelated error on 2nd click, also in new pre-debugger. Cheers, Henry
Re: [Pharo-project] Old bugs fixed by Opal
On Apr 19, 2013, at 1:56 PM, Marcus Denker wrote: > > On Apr 19, 2013, at 1:35 PM, Henrik Johansen > wrote: >>> >>> Did you use >>> >>> https://ci.inria.fr/rmod/job/Opal/ >>> >>> The Opal in the image is a bit out-dated… >> >> I did just now, but there, debugging *anything* (even 3 + 4, or using cmd >> dot) with the Opal Compiler set to default seemed to bring the image into a >> near catatonic state… >> Sort of hard to check if the buttons were fixed, with no debugger ever >> opening. ;) >> > > Yes, we committed some changes that might have broken things… > I will check. > Ok, found it… at least the debugger appears again after a "self halt" :-) https://ci.inria.fr/rmod/job/Opal/lastSuccessfulBuild/artifact/Opal.zip We should remember to never think it works before the regression tester is successful… Clement wrote a blog post: http://clementbera.wordpress.com/2013/03/22/toward-a-zero-bugs-interpreter-compiler/ Marcus
Re: [Pharo-project] Old bugs fixed by Opal
On Apr 19, 2013, at 1:35 PM, Henrik Johansen wrote: >>> >> >> Did you use >> >> https://ci.inria.fr/rmod/job/Opal/ >> >> The Opal in the image is a bit out-dated… > > I did just now, but there, debugging *anything* (even 3 + 4, or using cmd > dot) with the Opal Compiler set to default seemed to bring the image into a > near catatonic state… > Sort of hard to check if the buttons were fixed, with no debugger ever > opening. ;) > Yes, we committed some changes that might have broken things… I will check. Marcus
Re: [Pharo-project] Old bugs fixed by Opal
On Apr 19, 2013, at 12:34 PM, Marcus Denker wrote: > > On Apr 19, 2013, at 12:10 PM, Henrik Johansen > wrote: > >> >> On Apr 19, 2013, at 9:37 AM, Marcus Denker wrote: >> >>> Maybe of general interest… >>> >>> >>> Begin forwarded message: >>> Hi, These just work with Opal correctly: 7202 Errors when debugging inlined values https://pharo.fogbugz.com/f/cases/7202 750 Debugger highlight bug https://pharo.fogbugz.com/f/cases/750 :-) Marcus >>> >>> >>> (The list is here: >>> >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-compiler >>> >>> but this is more for boring things, e.g. commits to the repo and issue >>> tracker status mails) >>> >>> Marcus >> Oh, I *hate* 750! >> >> Tested it (ClosureTests new testToDoOutsideTemp -> debug) in the latest >> nightly, after switching to Opal the to:do: scope was indeed highlighted >> correctly :D >> .. however, I could not go into/over/through without incorrect >> highlighting/eventual error, I presume that is what the fix mentioned in >> issue coming later today is for? > > Did you use > > https://ci.inria.fr/rmod/job/Opal/ > > The Opal in the image is a bit out-dated… I did just now, but there, debugging *anything* (even 3 + 4, or using cmd dot) with the Opal Compiler set to default seemed to bring the image into a near catatonic state… Sort of hard to check if the buttons were fixed, with no debugger ever opening. ;) Cheers, Henry
