This is mostly feedback on using Debugger
- on DNU, if i press 'create a method' debugger opens, and shows extra (debugger related) context frames up to the method context which is just created. (while writing this, i found that it shows these extra contexts even if i simply press 'debug') : -------------- Process>>suspend OTToolset class>>debug:context:label:contents:fullView: OTToolset class>>debugError: [] in DEVToolSet class>>debugError: {[:obtools | obtools debugError: anError]} [] in DEVToolSet class>>ifOBTools:else: {[:obtools | aBlock value: obtools]} OTToolset class(Object)>>ifNil:ifNotNilDo: DEVToolSet class>>ifOBTools:else: DEVToolSet class>>debugError: ToolSet class>>debugError: UnhandledError>>defaultAction UndefinedObject>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: UnhandledError(Exception)>>signal UnhandledError class>>signalForException: Error>>defaultAction UndefinedObject>>handleSignal: Error(Exception)>>pass [] in PasteUpMorph>>becomeActiveDuring: {[:ex | ActiveWorld := priorWorld. ActiveEvent := priorEvent. ActiveHand :...]} BlockContext>>valueWithPossibleArgs: [] in MethodContext(ContextPart)>>handleSignal: {[(self tempAt: 2) valueWithPossibleArgs: {exception}]} BlockContext>>ensure: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: Error(Exception)>>signal Error(Exception)>>signal: ...... only here starts the context i'm interested in ..... ------------ - mistakenly clicked on 'proceed' while not saved the method caused a losing unsaved work - i'll be happy, to have 'create a method' button, when code throws #subclassResponsibility error :) -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
one more thing:
pressing 'restart' does not restarts evaluation from choosen context, and also throws me an error, when i previously created a new method by 'create method' button. (*sarcasm*) I think this build should be renamed to pharo-dev-dev , to indicate that this image is suitable for developing a development tools, like Debugger (*sarcasm end*) Nevertheless, you doing a great job guys! :) -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
This is the OB based debugger?
Stef On Feb 24, 2009, at 10:00 PM, Igor Stasenko wrote: > one more thing: > pressing 'restart' does not restarts evaluation from choosen context, > and also throws me an error, when i previously created a new method by > 'create method' button. > > (*sarcasm*) I think this build should be renamed to pharo-dev-dev , to > indicate that this image is suitable for developing a development > tools, like Debugger > (*sarcasm end*) > > Nevertheless, you doing a great job guys! :) > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
2009/2/24 Stéphane Ducasse <[hidden email]>:
> This is the OB based debugger? > Yeah, OTDebugger btw, how i can switch to old one? > Stef > On Feb 24, 2009, at 10:00 PM, Igor Stasenko wrote: > >> one more thing: >> pressing 'restart' does not restarts evaluation from choosen context, >> and also throws me an error, when i previously created a new method by >> 'create method' button. >> >> (*sarcasm*) I think this build should be renamed to pharo-dev-dev , to >> indicate that this image is suitable for developing a development >> tools, like Debugger >> (*sarcasm end*) >> >> Nevertheless, you doing a great job guys! :) >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Igor Stasenko
I'll take a look at your two (or three:) issues. Just for my info, what version of OB-Tools were you using?
Dale ----- "Igor Stasenko" <[hidden email]> wrote: | one more thing: | pressing 'restart' does not restarts evaluation from choosen context, | and also throws me an error, when i previously created a new method | by | 'create method' button. | | (*sarcasm*) I think this build should be renamed to pharo-dev-dev , | to | indicate that this image is suitable for developing a development | tools, like Debugger | (*sarcasm end*) | | Nevertheless, you doing a great job guys! :) | | | -- | Best regards, | Igor Stasenko AKA sig. | | _______________________________________________ | Pharo-project mailing list | [hidden email] | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
2009/2/25 Dale Henrichs <[hidden email]>:
> I'll take a look at your two (or three:) issues. Just for my info, what version of OB-Tools were you using? > OB-Tools-dkh.62 OmniBrowser-dr.441 OB-Standard-dr.339 OB-Enhancements-dr.310 > Dale > > ----- "Igor Stasenko" <[hidden email]> wrote: > > | one more thing: > | pressing 'restart' does not restarts evaluation from choosen context, > | and also throws me an error, when i previously created a new method > | by > | 'create method' button. > | > | (*sarcasm*) I think this build should be renamed to pharo-dev-dev , > | to > | indicate that this image is suitable for developing a development > | tools, like Debugger > | (*sarcasm end*) > | > | Nevertheless, you doing a great job guys! :) > | > | > | -- > | Best regards, > | Igor Stasenko AKA sig. > | > | _______________________________________________ > | Pharo-project mailing list > | [hidden email] > | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Igor Stasenko
----- "Igor Stasenko" <[hidden email]> wrote: | one more thing: | pressing 'restart' does not restarts evaluation from choosen context, | and also throws me an error, when i previously created a new method | by | 'create method' button. Igor, I can see the 'extra contexts' that you reported in your other message, but I don't seem to be able to reproduce the above problem. Pressing 'restart' trims the stack and doesn't throw an error when I try it (using OB-Tools-dkh.62)... Could you reproduce the bug and supply an 'error report' for the stack error that you get, so I can get a better idea of what the problem may be. Dale _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
2009/2/25 Dale Henrichs <[hidden email]>:
> > ----- "Igor Stasenko" <[hidden email]> wrote: > > | one more thing: > | pressing 'restart' does not restarts evaluation from choosen context, > | and also throws me an error, when i previously created a new method > | by > | 'create method' button. > > Igor, > > I can see the 'extra contexts' that you reported in your other message, but I don't seem to be able to reproduce the above problem. > > Pressing 'restart' trims the stack and doesn't throw an error when I try it (using OB-Tools-dkh.62)... > > Could you reproduce the bug and supply an 'error report' for the stack error that you get, so I can get a better idea of what the problem may be. > Weird.. seems like i'm too lucky in finding bugs :) Okay, here is how to reproduce it. Download following image: http://gforge.inria.fr/frs/download.php/18192/pharo0.1-10243dev09.02.3.zip open workspace and do it: nil sendweirdmessage when debugger pops up, press 'create new method' and see the stack with 'extra contexts' you can press 'debug' instead and still see these contexts. > Dale > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Igor Stasenko
----- "Igor Stasenko" <[hidden email]> wrote: | 2009/2/25 Dale Henrichs <[hidden email]>: | > | > ----- "Igor Stasenko" <[hidden email]> wrote: | > | > | one more thing: | > | pressing 'restart' does not restarts evaluation from choosen | context, | > | and also throws me an error, when i previously created a new | method | > | by | > | 'create method' button. | > | > Igor, | > | > I can see the 'extra contexts' that you reported in your other | message, but I don't seem to be able to reproduce the above problem. | > | > Pressing 'restart' trims the stack and doesn't throw an error when I | try it (using OB-Tools-dkh.62)... | > | > Could you reproduce the bug and supply an 'error report' for the | stack error that you get, so I can get a better idea of what the | problem may be. | > | | Weird.. seems like i'm too lucky in finding bugs :) | | Okay, here is how to reproduce it. | Download following image: | | http://gforge.inria.fr/frs/download.php/18192/pharo0.1-10243dev09.02.3.zip | | open workspace and do it: | | nil sendweirdmessage | | when debugger pops up, press 'create new method' and see the stack | with 'extra contexts' | you can press 'debug' instead and still see these contexts. Igor, I _am_ able to reproduce the extra contexts ... I _have_ seen the extra contexts with debug: and 'create method'. _However_, you reported that you got an error when pressing 'restart' in that situation and I am not able to reproduce the error ... it is that error that I would like help in reproducing. When I press 'restart' I don't get an error. When I proceed, I see the default #shouldBeImplemented error, but I assumed you were talking about an error occurring when you press the 'restart' button. Dale _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
2009/2/25 Dale Henrichs <[hidden email]>:
> > ----- "Igor Stasenko" <[hidden email]> wrote: > > | 2009/2/25 Dale Henrichs <[hidden email]>: > | > > | > ----- "Igor Stasenko" <[hidden email]> wrote: > | > > | > | one more thing: > | > | pressing 'restart' does not restarts evaluation from choosen > | context, > | > | and also throws me an error, when i previously created a new > | method > | > | by > | > | 'create method' button. > | > > | > Igor, > | > > | > I can see the 'extra contexts' that you reported in your other > | message, but I don't seem to be able to reproduce the above problem. > | > > | > Pressing 'restart' trims the stack and doesn't throw an error when I > | try it (using OB-Tools-dkh.62)... > | > > | > Could you reproduce the bug and supply an 'error report' for the > | stack error that you get, so I can get a better idea of what the > | problem may be. > | > > | > | Weird.. seems like i'm too lucky in finding bugs :) > | > | Okay, here is how to reproduce it. > | Download following image: > | > | http://gforge.inria.fr/frs/download.php/18192/pharo0.1-10243dev09.02.3.zip > | > | open workspace and do it: > | > | nil sendweirdmessage > | > | when debugger pops up, press 'create new method' and see the stack > | with 'extra contexts' > | you can press 'debug' instead and still see these contexts. > > Igor, > > I _am_ able to reproduce the extra contexts ... I _have_ seen the extra contexts with debug: and 'create method'. > > _However_, you reported that you got an error when pressing 'restart' in that situation and I am not able to reproduce the error ... it is that error that I would like help in reproducing. When I press 'restart' I don't get an error. > > When I proceed, I see the default #shouldBeImplemented error, but I assumed you were talking about an error occurring when you press the 'restart' button. > Hmm. i can't reproduce it myself. It pops up the message , like 'unable to restart context' or something.. but not an error which can be debugged. Seem like debugger catching this case by itself and simply asserts you from doing wrong action. But i just debugging my code, nothing else.. This message pops up some times, sometimes its fine. This is why i calling it error (or bug). I will continue hacking my code for more longer until i get this error.. > Dale > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
----- "Igor Stasenko" <[hidden email]> wrote: | Hmm. i can't reproduce it myself. | It pops up the message , like 'unable to restart context' or | something.. | but not an error which can be debugged. Seem like debugger catching | this case by itself and simply asserts you from doing wrong action. | But i just debugging my code, nothing else.. This message pops up | some | times, sometimes its fine. This is why i calling it error (or bug). | I will continue hacking my code for more longer until i get this | error.. Okay, This helps - I have some error conditions to look for. Dale _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Igor Stasenko
On Tue, Feb 24, 2009 at 10:33 PM, Igor Stasenko <[hidden email]> wrote:
> btw, how i can switch to old one? Have a look at the DevToolSet class (class-side). There is something like an #ifOB:else: method. -- Damien Cassou http://damiencassou.seasidehosting.st _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
2009/2/25 Damien Cassou <[hidden email]>:
> On Tue, Feb 24, 2009 at 10:33 PM, Igor Stasenko <[hidden email]> wrote: >> btw, how i can switch to old one? Toolset askForDefault > > Have a look at the DevToolSet class (class-side). There is something > like an #ifOB:else: method. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Cédrick _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Yeah, i found it already
2009/2/25 Cédrick Béler <[hidden email]>: > 2009/2/25 Damien Cassou <[hidden email]>: >> On Tue, Feb 24, 2009 at 10:33 PM, Igor Stasenko <[hidden email]> wrote: >>> btw, how i can switch to old one? > > > Toolset askForDefault > > >> >> Have a look at the DevToolSet class (class-side). There is something >> like an #ifOB:else: method. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Cédrick > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Igor Stasenko
Okay,
I've been able to reproduce the spurious bug that Igor was seeing ('aContext not in process chain' error). It seems to be related to the fact that the OTDebugger uses an OBFixedButtonPanel and the buttons are not getting updated correctly (or at all), so the buttons are operating on stale contexts. The menu items for the debugger appear to work okay - although the short cut keys may not work - I'll look into this one:). You'll hit the 'aContext not in process chain' as soon as you step out of the original method context. The problem was introduced with pharo0.1-10243dev09.02.3 (pharo0.1-10236dev09.02.2 doesn't have the sticky button problem). I also have fixes for the extra junk on the stack (for create method and for halts/errors), but until the OBFixedButtonPanel issue gets fixed you might want to revert to the non-ob debugger. Dale _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Ok dale
this is probably related to the problems I see too during the lab. if you have fix open an issue in the bugtracker and post here so that we get aware of it. Stef On Feb 25, 2009, at 3:46 PM, Dale Henrichs wrote: > Okay, > > I've been able to reproduce the spurious bug that Igor was seeing > ('aContext not in process chain' error). > > It seems to be related to the fact that the OTDebugger uses an > OBFixedButtonPanel and the buttons are not getting updated correctly > (or at all), so the buttons are operating on stale contexts. The > menu items for the debugger appear to work okay - although the short > cut keys may not work - I'll look into this one:). You'll hit the > 'aContext not in process chain' as soon as you step out of the > original method context. > > The problem was introduced with pharo0.1-10243dev09.02.3 > (pharo0.1-10236dev09.02.2 doesn't have the sticky button problem). > > I also have fixes for the extra junk on the stack (for create method > and for halts/errors), but until the OBFixedButtonPanel issue gets > fixed you might want to revert to the non-ob debugger. > > Dale > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Igor Stasenko
Stef,
I posted a more detailed problem description to the OmniBrowser list and David has an update that fixes the problem (in OmniBrowser-dr.442). I'll verify the fix later today. Presumably OmniBrowser-dr.442 will be included in the next development drop, if not I will submit a bug. Dale ----- "Stéphane Ducasse" <[hidden email]> wrote: | Ok dale | this is probably related to the problems I see too during the lab. | if you have fix open an issue in the bugtracker and post here so that | | we get aware of it. | | Stef _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Dale
----- "Dale Henrichs" <[hidden email]> wrote: | Okay, | | I've been able to reproduce the spurious bug that Igor was seeing | ('aContext not in process chain' error). | | It seems to be related to the fact that the OTDebugger uses an | OBFixedButtonPanel and the buttons are not getting updated correctly | (or at all), so the buttons are operating on stale contexts. The menu | items for the debugger appear to work okay - although the short cut | keys may not work - I'll look into this one:). You'll hit the | 'aContext not in process chain' as soon as you step out of the | original method context. | | The problem was introduced with pharo0.1-10243dev09.02.3 | (pharo0.1-10236dev09.02.2 doesn't have the sticky button problem). | | I also have fixes for the extra junk on the stack (for create method | and for halts/errors), but until the OBFixedButtonPanel issue gets | fixed you might want to revert to the non-ob debugger. | | Dale If you want to try the OTDebugger in pharo0.1-10243dev09.02.3 or later you can manually update OmniBrowser-dr.442 and OB-Tools-dkh.65 (which has fixes for the bugs reported by Igor). Dale _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Igor Stasenko
> OB-Tools-dkh.62 > OmniBrowser-dr.441 > OB-Standard-dr.339 > OB-Enhancements-dr.310 Just curious: Did you load this versions by hand? Because those versions of OB are still alpha, so we have to expect dev-dev behavior in those. ;) David _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
On Thu, Feb 26, 2009 at 10:07 PM, David Röthlisberger
<[hidden email]> wrote: > Just curious: Did you load this versions by hand? Because those versions of OB are > still alpha, so we have to expect dev-dev behavior in those. ;) pharo-dev is now based on #loadOBAlpha. -- Damien Cassou http://damiencassou.seasidehosting.st _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Free forum by Nabble | Edit this page |