[Pharo-project] Wrong values of variables showed in execution context when doing self break?
This is another one that is weird. When I debug some code by introducing a self break statement, I usually get the values of the variables shown in the bottom of the debugger all messed up. It should be noted that "doiting" something which has self break opens a different debugger than debuging code directly. Here is an example to reproduce it. Maybe somebody has already opened a ticket for this problem. To try you can doit the following code and look at the values shown of x and y in the bottom left list of debugger. AClassToTest doSomeThingWith: 14@17. after creating AClassToTest: 'From Pharo0.1 of 16 May 2008 [Latest update: #10373] on 4 August 2009 at 1:07:23 am'! Object subclass: #AClassToTest instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'BreakPointBroken'! "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! AClassToTest class instanceVariableNames: ''! !AClassToTest class methodsFor: 'as yet unclassified' stamp: 'JEP 8/4/2009 00:29'! do: aBoolean ifTrue: tBlock ifFalse: fBlock aBoolean ifTrue: tBlock ifFalse: fBlock. ^true. ! ! !AClassToTest class methodsFor: 'as yet unclassified' stamp: 'JEP 8/4/2009 00:53'! doSomeThingWith: aPoint | x y | self break. self do: false ifTrue: [ x := aPoint x. y := aPoint y. ] ifFalse: [ 1 + 1. ]. ^x. ! ! -- Javier Pimás Ciudad de Buenos Aires
2009/8/4 Javier Pimás <elpochodelagente@gmail.com>:
Here is an example to reproduce it. Maybe somebody has already opened a ticket for this problem. To try you can doit the following code and look at the values shown of x and y in the bottom left list of debugger.
AClassToTest doSomeThingWith: 14@17.
I can't reproduce your bug. Please try again in a 10402 image or later and open an issue tagged Milestone-1.0 if you can still reproduce it. Also attach the code to the issue so that people can load easily. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
On Tue, Aug 4, 2009 at 8:24 AM, Damien Cassou <damien.cassou@gmail.com>wrote:
2009/8/4 Javier Pimás <elpochodelagente@gmail.com>:
Here is an example to reproduce it. Maybe somebody has already opened a ticket for this problem. To try you can doit the following code and look
at
the values shown of x and y in the bottom left list of debugger.
AClassToTest doSomeThingWith: 14@17.
I can't reproduce your bug. Please try again in a 10402 image or later and open an issue tagged Milestone-1.0 if you can still reproduce it. Also attach the code to the issue so that people can load easily.
I also did it but didn't find something strange. Perhaps a screenshot may help. best, mariano
-- Damien Cassou http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I tested in latest (pharo1.0beta-10401web09.07.5) and noticed that now pharo uses the same debugger for breakpoints and for "debugits", which is nice. The bug I mentioned seems to be in OTDebugger, which has been removed from the image, so it could be said it's "fixed". Now, this debugger has ooother problem... if doing the same as before (AClassToTest doSomeThingWith: 14@17) in the bottom right list appears " stack top", and if I click it, an error pops up (AClassToTest DNU: #asText). So what happened with #asText? Also more questions: with this debugger there isn't any step out button, nor a return one, which I found useful often. Is this going to stay that way? Another thing I noticed is that OBPackageBrowser has also been removed, and the actual class browser doesn't have a search bar on top. How do you search for a class if you don't know in what package is defined? I feel really lost without the search bar... Thanks, Javier. 2009/8/4 Mariano Martinez Peck <marianopeck@gmail.com>
On Tue, Aug 4, 2009 at 8:24 AM, Damien Cassou <damien.cassou@gmail.com>wrote:
2009/8/4 Javier Pimás <elpochodelagente@gmail.com>:
Here is an example to reproduce it. Maybe somebody has already opened a ticket for this problem. To try you can doit the following code and look
at
the values shown of x and y in the bottom left list of debugger.
AClassToTest doSomeThingWith: 14@17.
I can't reproduce your bug. Please try again in a 10402 image or later and open an issue tagged Milestone-1.0 if you can still reproduce it. Also attach the code to the issue so that people can load easily.
I also did it but didn't find something strange. Perhaps a screenshot may help.
best,
mariano
-- Damien Cassou http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Javier Pimás Ciudad de Buenos Aires
On Aug 5, 2009, at 5:29 PM, Javier Pimás wrote:
I tested in latest (pharo1.0beta-10401web09.07.5) and noticed that now pharo uses the same debugger for breakpoints and for "debugits", which is nice. The bug I mentioned seems to be in OTDebugger, which has been removed from the image, so it could be said it's "fixed".
Now, this debugger has ooother problem... if doing the same as before (AClassToTest doSomeThingWith: 14@17) in the bottom right list appears " stack top", and if I click it, an error pops up (AClassToTest DNU: #asText). So what happened with #asText?
Also more questions: with this debugger there isn't any step out button, nor a return one, which I found useful often. Is this going to stay that way?
No idea. this is the OTDebugger and I do not know who is maintaining it. May be dale?
Another thing I noticed is that OBPackageBrowser has also been removed, and the actual class browser doesn't have a search bar on top. How do you search for a class if you don't know in what package is defined? I feel really lost without the search bar...
you select the category pane and cmd-F then type the name of the class and you get it.
Thanks, Javier.
2009/8/4 Mariano Martinez Peck <marianopeck@gmail.com>
On Tue, Aug 4, 2009 at 8:24 AM, Damien Cassou <damien.cassou@gmail.com> wrote: 2009/8/4 Javier Pimás <elpochodelagente@gmail.com>:
Here is an example to reproduce it. Maybe somebody has already
opened a
ticket for this problem. To try you can doit the following code and look at the values shown of x and y in the bottom left list of debugger.
AClassToTest doSomeThingWith: 14@17.
I can't reproduce your bug. Please try again in a 10402 image or later and open an issue tagged Milestone-1.0 if you can still reproduce it. Also attach the code to the issue so that people can load easily.
I also did it but didn't find something strange. Perhaps a screenshot may help.
best,
mariano
--
Damien Cassou http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Javier Pimás Ciudad de Buenos Aires _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Stef and Javier, I am maintaining the OTDebugger and have been addressing problems as they are reported. When you originally reported the bug I (mistakenly) thought you had been using the old debugger since that is the debugger shipped with the 1.0beta. I'm somewhat hammered at the moment, but I will take a look at the problem when I get a chance. Dale ----- "Stéphane Ducasse" <stephane.ducasse@inria.fr> wrote: | On Aug 5, 2009, at 5:29 PM, Javier Pimás wrote: | | > I tested in latest (pharo1.0beta-10401web09.07.5) and noticed that | | > now pharo uses the same debugger for breakpoints and for "debugits", | | > which is nice. The bug I mentioned seems to be in OTDebugger, which | | > has been removed from the image, so it could be said it's "fixed". | > | > Now, this debugger has ooother problem... if doing the same as | > before (AClassToTest doSomeThingWith: 14@17) in the bottom right | > list appears " stack top", and if I click it, an error pops up | > (AClassToTest DNU: #asText). So what happened with #asText? | > | > Also more questions: with this debugger there isn't any step out | > button, nor a return one, which I found useful often. Is this going | | > to stay that way? | | No idea. | this is the OTDebugger and I do not know who is maintaining it. | May be dale? | > | > Another thing I noticed is that OBPackageBrowser has also been | > removed, and the actual class browser doesn't have a search bar on | | > top. How do you search for a class if you don't know in what package | | > is defined? I feel really lost without the search bar... | | you select the category pane and cmd-F | then type the name of the class and you get it. | | > | > Thanks, | > Javier. | > | > 2009/8/4 Mariano Martinez Peck <marianopeck@gmail.com> | > | > | > On Tue, Aug 4, 2009 at 8:24 AM, Damien Cassou | > <damien.cassou@gmail.com> wrote: | > 2009/8/4 Javier Pimás <elpochodelagente@gmail.com>: | > > | > > Here is an example to reproduce it. Maybe somebody has already | > opened a | > > ticket for this problem. To try you can doit the following code | > and look at | > > the values shown of x and y in the bottom left list of debugger. | > > | > > AClassToTest doSomeThingWith: 14@17. | > | > I can't reproduce your bug. Please try again in a 10402 image or | later | > and open an issue tagged Milestone-1.0 if you can still reproduce | it. | > Also attach the code to the issue so that people can load easily. | > | > | > I also did it but didn't find something strange. Perhaps a | > screenshot may help. | > | > best, | > | > mariano | > | > | > | > -- | > | > Damien Cassou | > http://damiencassou.seasidehosting.st | > | > "Lambdas are relegated to relative obscurity until Java makes them | > popular by not having them." James Iry | > | > _______________________________________________ | > Pharo-project mailing list | > Pharo-project@lists.gforge.inria.fr | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | > | > | > _______________________________________________ | > Pharo-project mailing list | > Pharo-project@lists.gforge.inria.fr | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | > | > | > | > -- | > Javier Pimás | > Ciudad de Buenos Aires | > _______________________________________________ | > Pharo-project mailing list | > Pharo-project@lists.gforge.inria.fr | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2009/8/5 Javier Pimás <elpochodelagente@gmail.com>
I tested in latest (pharo1.0beta-10401web09.07.5) and noticed that now pharo uses the same debugger for breakpoints and for "debugits", which is nice. The bug I mentioned seems to be in OTDebugger, which has been removed from the image, so it could be said it's "fixed".
Now, this debugger has ooother problem... if doing the same as before (AClassToTest doSomeThingWith: 14@17) in the bottom right list appears " stack top", and if I click it, an error pops up (AClassToTest DNU: #asText). So what happened with #asText?
Please. Open a bug ticket. I saw this one: http://code.google.com/p/pharo/issues/detail?id=724 seems similar but not the same.
Also more questions: with this debugger there isn't any step out button, nor a return one, which I found useful often. Is this going to stay that way?
It is a matter of the toolset. OBPackageBrowser and all that staff were removed from the image because they were very slow. We decided to remove them until they are fast enought. However, you can install them and set them as default is you want. Does someone know how can I install OBPackageBrowser and that ToolSet ? the one that was used before ? It would be nice to put that piece of code in here: http://code.google.com/p/pharo/wiki/CodeSnippets
Another thing I noticed is that OBPackageBrowser has also been removed, and the actual class browser doesn't have a search bar on top. How do you search for a class if you don't know in what package is defined? I feel really lost without the search bar...
See stef answer or install OBPackageBrowser
Thanks, Javier.
2009/8/4 Mariano Martinez Peck <marianopeck@gmail.com>
On Tue, Aug 4, 2009 at 8:24 AM, Damien Cassou <damien.cassou@gmail.com>wrote:
2009/8/4 Javier Pimás <elpochodelagente@gmail.com>:
Here is an example to reproduce it. Maybe somebody has already opened a ticket for this problem. To try you can doit the following code and
look at
the values shown of x and y in the bottom left list of debugger.
AClassToTest doSomeThingWith: 14@17.
I can't reproduce your bug. Please try again in a 10402 image or later and open an issue tagged Milestone-1.0 if you can still reproduce it. Also attach the code to the issue so that people can load easily.
I also did it but didn't find something strange. Perhaps a screenshot may help.
best,
mariano
-- Damien Cassou http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Javier Pimás Ciudad de Buenos Aires
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2009/8/5 Mariano Martinez Peck <marianopeck@gmail.com>:
Does someone know how can I install OBPackageBrowser and that ToolSet ? the one that was used before ? It would be nice to put that piece of code in here: http://code.google.com/p/pharo/wiki/CodeSnippets
That's currently not possible to install the package browser in a Pharo non-core image. Please wait a bit for David, Lukas and Colin to decide how to continue OB development. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
2009/8/5 Javier Pimás <elpochodelagente@gmail.com>:
Now, this debugger has ooother problem... if doing the same as before (AClassToTest doSomeThingWith: 14@17) in the bottom right list appears " stack top", and if I click it, an error pops up (AClassToTest DNU: #asText). So what happened with #asText?
This is already reported at http://code.google.com/p/pharo/issues/detail?id=987
Also more questions: with this debugger there isn't any step out button, nor a return one, which I found useful often. Is this going to stay that way?
There is no step out but there is a 'return entered value' if you right click on the context line. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
participants (5)
-
Dale Henrichs -
Damien Cassou -
Javier Pimás -
Mariano Martinez Peck -
Stéphane Ducasse