- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 1546 in pharo: rescue chat note
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Updates: Status: Closed Comment #4 on issue 1546 by marcus.d...(a)gmail.com: rescue chat note http://code.google.com/p/pharo/issues/detail?id=1546 It's a StringHolder subclass!! kill, kill.... ;-)

1 0

[Pharo-project] Issue 3788 in pharo: Should fix all the menu category of ToolRegistry and deprecate the methods.
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Status: Accepted Owner: siguc...(a)gmail.com Labels: Milestone-1.3 New issue 3788 by siguc...(a)gmail.com: Should fix all the menu category of ToolRegistry and deprecate the methods. http://code.google.com/p/pharo/issues/detail?id=3788 The category 'menu' is just for backward compatibility. The methods should be deprecated.

1 2

Re: [Pharo-project] [Vm-dev] Debugging Cog crash
by Schwab,Wilhelm K April 8, 2011

April 8, 2011

Levente, It is indeed not the UUID plugin - Dave already suggested deleting it, and I tried that w/o success. As for running gdb, I will gladly do so, but I have zero experience with it. The most relevant posts I can find mention attaching to a vm that is already running, and I can't get that far. Below is my attempt to modify the one-click shell script to run the vm under gdb. Perhaps you or someone else can show me the errors of my ways and produce something that would yield a callstack. Bill #!/bin/sh # path ROOT=`dirname $0` LINUX="$ROOT/Contents/Linux" RESOURCES="$ROOT/Contents/Resources" # icon gvfs-set-attribute \ "$0" \ "metadata::custom-icon" \ "file://$RESOURCES/Squeak.png" \ 2> /dev/null # execute gdb "$LINUX/squeakvm" gdb run -plugins "$LINUX" \ -encoding latin1 \ -vm-display-X11 \ "$RESOURCES/Pharo.image" Levente wrote: Well, the file OneClick.txt says the vm is "Linux Intel x86 4.0.3.2202". But that's not true, because that's not a CogVM. The UUIDPlugin seems to have the patch which avoids the crash, so it's pretty unlikely that it's an issue with the UUIDPlugin. Even if the patch is wrong (which is unlikely, because we're using Eliot's latest build on 64-bit Ubuntu 8.04 and it doesn't crash, but previous unpatched builds did crash), it's pretty unlikely that the cause of the crash is the related to UUIDPlugin at all, because UUIDs are normally not created during startup and your image is crashing on startup. To be 100% sure you can try deleting UUIDPlugin and see if your image is crashing or not. If it still crashes, then use gdb to see where it crashes. The VM seems to be unstripped (8MB), so it should be easy to identify the cause of the crash. Levente ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K [bschwab(a)anest.ufl.edu] Sent: Friday, April 08, 2011 11:56 AM To: Pharo-project(a)lists.gforge.inria.fr; Squeak Virtual Machine Development Discussion Subject: Re: [Pharo-project] [Vm-dev] FW: Debugging Cog crash Levente, The image will not load at all. It simply dies with "Segmentation fault" - NOTHING else happens. gdb is maybe a possibility, but it is not an approach I ordinarily take, so some guidance would be helpful. I have a reproducible crash, but poor access to the affected box. Bill On Fri, 8 Apr 2011, Schwab,Wilhelm K wrote: > > Gratuitous default recipient... > > If there is a verbose dump option or other diagnostic efforts that will help, I will do my best to run them and report the results. I am fairly certain the vm is 'Croquet Closure Cog VM [CoInterpreter VMMaker-oscog.54]' (can verify later today), but this happened with an earlier Cog one-click too. There is something about the machine (UUID again?) that is different. I do not have root access to it, but I can get to a terminal. Ubuntu 10.10. Where did you download the VM? Does it crash when you're trying to evaluate [UUID new]? Did you try gdb? Levente ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K [bschwab(a)anest.ufl.edu] Sent: Friday, April 08, 2011 11:42 AM To: Pharo-project(a)lists.gforge.inria.fr; Squeak Virtual Machine Development Discussion Subject: Re: [Pharo-project] [Vm-dev] FW: Debugging Cog crash Dave, It was, I did :) No help :( What else can I try? Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of David T. Lewis [lewis(a)mail.msen.com] Sent: Friday, April 08, 2011 10:32 AM To: Squeak Virtual Machine Development Discussion Cc: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [Vm-dev] FW: Debugging Cog crash Yes, the libuuid.so bug would be a likely suspect. If the UUIDPlugin was built as an external library, just delete it and you will probably be good to go. If you need further info, look here: http://bugs.squeak.org/view.php?id=7358 Dave On Fri, Apr 08, 2011 at 07:58:39AM -0400, Schwab,Wilhelm K wrote: > > Gratuitous default recipient... > > If there is a verbose dump option or other diagnostic efforts that will help, I will do my best to run them and report the results. I am fairly certain the vm is 'Croquet Closure Cog VM [CoInterpreter VMMaker-oscog.54]' (can verify later today), but this happened with an earlier Cog one-click too. There is something about the machine (UUID again?) that is different. I do not have root access to it, but I can get to a terminal. Ubuntu 10.10. > > > ________________________________________ > From: Schwab,Wilhelm K > Sent: Friday, April 08, 2011 7:44 AM > To: Mariano Martinez Peck > Subject: RE: [Pharo-project] Debugging Cog crash > > Mariano, > > I first identified this problem/opportunity a while ago. At the time, there was no log - the vm just died. I can sniff around again as there might be one this time. My question at the time was whether there was something that I could enable to perhaps get more info. > > The output from the vm is, and I quote<g> "Segmentation fault". There is no other output. Perhaps it does not get far enough to have a call stack?? > > Bill > > > > ________________________________________ > From: Mariano Martinez Peck [marianopeck(a)gmail.com] > Sent: Friday, April 08, 2011 3:42 AM > To: Squeak Development Discussion Virtual Machine; Pharo Development > Cc: Schwab,Wilhelm K > Subject: Re: [Pharo-project] Debugging Cog crash > > also...shouldn't be a crash/dump file somewhere? > > can you write the output of the console where you invoke the VM into a file ? (using > to redirect) > > Cheers > > Mariano > > On Thu, Apr 7, 2011 at 11:10 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: > Hello all, > > I have an account on an Ubuntu terminal server (at least I think that's what it would be called) running 10.10. The Cog one-click image crashes with "Segmentation fault" (if run from a terminal); the legacy VM seems to run the image nicely on the box. Any ideas? I will happily collect any facts that will be of help, but I need some > direction. > > Bill > > > > > > > -- > Mariano > http://marianopeck.wordpress.com

1 0

[Pharo-project] An idea about Pluggable widgets
by Igor Stasenko April 8, 2011

April 8, 2011

I have an idea how to refactor the pluggable morphs mess. The main principle behind all pluggables, that you have a model (which is held in instance variable), and then morph having additional ivars to speak with this model, which the selector names you should use to access certain state from model. For example: AlignmentMorph subclass: #PluggableButtonMorph instanceVariableNames: 'model label getStateSelector actionSelector getLabelSelector getMenuSelector shortcutCharacter askBeforeChanging triggerOnMouseDown offColor onColor feedbackColor showSelectionFeedback allButtons arguments argumentsProvider argumentsSelector gradientLook enabled actionBlock getColorSelector getEnabledSelector' classVariableNames: 'UseGradientLook' poolDictionaries: '' category: 'Morphic-Pluggable Widgets' as you can see it is crowded with all those ivars, where part of them used to speak with model, and part of them used for keeping flags and additional parameters which you can customize when creating a button. getStateSelector actionSelector getLabelSelector getMenuSelector arguments argumentsProvider argumentsSelector gradientLook actionBlock getColorSelector getEnabledSelector and this is really messy.. Take a look at code: performAction "Inform the model that this button has been pressed. Sent by the controller when this button is pressed. If the button's actionSelector takes any arguments, they are obtained dynamically by sending the argumentSelector to the argumentsProvider" enabled ifFalse: [^self]. askBeforeChanging ifTrue: [model okToChange ifFalse: [^ self]]. self actionBlock ifNotNil: [ ^ self actionBlock value]. actionSelector ifNotNil: [actionSelector numArgs == 0 ifTrue: [model perform: actionSelector] ifFalse: [argumentsProvider ifNotNil: [arguments := argumentsProvider perform: argumentsSelector]. model perform: actionSelector withArguments: arguments]] Now think if we could replace this with simple: performAction "Inform the model that this button has been pressed. Sent by the controller when this button is pressed. If the button's actionSelector takes any arguments, they are obtained dynamically by sending the argumentSelector to the argumentsProvider" enabled ifFalse: [^self]. model performAction. so, in this case, we just put an obligation onto model to perform any action in response to button clicked, and button no longer cares about crappy logic how it should send a message to model (via action block, via actionSelector ... and whether it should pass any additional arguments or not..) So, in all places which using things in a way like: getListItems ^ model perform: getListItemsSelector now will be replaced with clean: getListItems ^ model getListItems So, a pluggable morph no longer cares about keeping all those selectors and maintain an obscure logic whether selector is nil or not nil etc etc.. Let model handle it! Then you may ask, what if i have a model, which doesn't implements such protocol (required for specific pluggable widget). The answer is simple: - create a pluggable model class for given widget, which wraps around your object and can keeps all those messy 'getLabelSelector' 'getMenuSelector' , inside and mediates between your model and widget. The benefit of it that widgets code will be much more cleaner. And another benefit is that you know what exact protocol is needed if you want to use your object as a model to given widget (list, button etc). And in most of the cases, you don't need to use this messy 'getXYZSelector', because you can simply answer to messages sent by widget and provide necessary data. But if you wanna go messy, you just use wrapper model, which contains all those 'getXYZSelectors' which you can set to whatever you like. -- Best regards, Igor Stasenko AKA sig.

5 8

[Pharo-project] Issue 3971 in pharo: OBSystemBrowserAdaptor does not correctly find classes
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Status: New Owner: ---- New issue 3971 by DougEdmu...(a)gmail.com: OBSystemBrowserAdaptor does not correctly find classes http://code.google.com/p/pharo/issues/detail?id=3971 Using: Pharo1.2.2a Latest update: #12346 on XP ObSystemBrowserAdaptor (the "System Browser" window) does not correctly find classes: 1. Open system browser, right click, select "Find Classes". 2. Type in 'button' 3. Results include classes that do not contain 'button'. (such as the first entry, "AbstractAutotestTestLongRun")

1 4

[Pharo-project] [COTDC] 44 - ColorChanged
by laurent laffont April 8, 2011

April 8, 2011

Today: ColorChanged Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

1 1

[Pharo-project] RPackage not updated when adding a category
by Cyrille Delaunay April 8, 2011

April 8, 2011

This is maybe related to SystemOrganizer>>addCategory:before: which seems to never notify that a category has been added (whereas SystemOrganizer>>addCategory: does it). I opened an issue : http://code.google.com/p/pharo/issues/detail?id=3974

1 0

[Pharo-project] Issue 3974 in pharo: [RPackage] rpackage do not update when adding a category
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Status: Accepted Owner: cy.delau...(a)gmail.com New issue 3974 by cy.delau...(a)gmail.com: [RPackage] rpackage do not update when adding a category http://code.google.com/p/pharo/issues/detail?id=3974 In a 1.3 image, When I add a category to the default browser, RPackage is not updated accordingly, it does not register the new package. Adding a category in the default browser will send addCategory:before: to SystemOrganizer , which never emit any event (contrary to SystemOrganizer>>addCategory:). Therefore RPackage is never aware of any change. Should add a notification in SystemOrganizer>>addCategory?

1 0

[Pharo-project] Issue 3544 in pharo: Rename Morphic-Themes into Themes
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Status: Accepted Owner: stephane...(a)gmail.com Labels: Milestone-1.2 New issue 3544 by stephane...(a)gmail.com: Rename Morphic-Themes into Themes http://code.google.com/p/pharo/issues/detail?id=3544 we should rename the Morphic-Themes package into what: Themes?

1 3

[Pharo-project] [update 1.3] #13136
by Marcus Denker April 8, 2011

April 8, 2011

13136 ----- Issue 3969: MorphTreeMorph performance Issue 3870: [Failing Test] 1.3 KernelTests.Methods.CompiledMethodTest.testNew -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0