April 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] CogVM segmentation fault (on linux) when running headless

by StÃ©phane Ducasse

sebastian can you open a bug entry? thanks Stef On Apr 6, 2012, at 4:06 AM, Sebastian Sastre wrote: > Hi guys, > > I'm testing CogVM for one airflowing worker we have in stage and it looks quite promising when we start the image with UI but when we start it headless it immediately segfaults > > Below is the log > > sebastian > > o/ > > > :~$ sudo invoke-rc.d airflowing0 start > :~$ > Segmentation fault Thu Apr 5 21:00:09 2012 > > > Squeak VM version: 3.9-7 #1 Thu Apr 5 14:40:40 CEST 2012 gcc 4.1.2 > Built from: CoInterpreter VMMaker-oscog-EstebanLorenzano.139 uuid: 5aa53979-d7d8-4ca3-91fe-cfc3b4109c33 Apr 5 2012 > With: StackToRegisterMappingCogit VMMaker-oscog-EstebanLorenzano.139 uuid: 5aa53979-d7d8-4ca3-91fe-cfc3b4109c33 Apr 5 2012 > Revision: https://git.gitorious.org/cogvm/blessed.git Commit: 846551630c3c10df1f59588a6e7131d602f00b45 Date: Thu Apr 5 14:13:41 2012 +0200 By: Esteban Lorenzano <estebanlm(a)gmail.com> > Build host: Linux pharo-build.lille.inria.fr 2.6.18-194.26.1.el5xen #1 SMP Tue Nov 9 14:13:46 EST 2010 i686 i686 i386 GNU/Linux > plugin path: /home/prod/pharo/cog/ [default: /home/prod/pharo/cog/] > > > C stack backtrace: > /home/prod/pharo/cog/CogVM[0x80968b1] > /home/prod/pharo/cog/CogVM[0x8096a52] > [0xb77a8440] > /lib/tls/i686/cmov/libc.so.6(iconv+0x6e)[0xb761e4ee] > /home/prod/pharo/cog/CogVM(convertChars+0xb4)[0x8094384] > /home/prod/pharo/cog/CogVM(sq2uxPath+0x47)[0x80945d7] > /home/prod/pharo/cog/CogVM(dir_Lookup+0x73)[0x80b8703] > /home/prod/pharo/cog/CogVM[0x80b7180] > /home/prod/pharo/cog/CogVM(interpret+0x3f68)[0x808dcc8] > /home/prod/pharo/cog/CogVM[0x808fc97] > /home/prod/pharo/cog/CogVM[0x8090664] > /home/prod/pharo/cog/CogVM(main+0x38a)[0x809774a] > /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb761d460] > /home/prod/pharo/cog/CogVM[0x805acc1] > > > Smalltalk stack dump: > 0xbfdc45d8 I FSUnixStore(FSDiskStore)>directoryAt:ifAbsent:nodesDo: -1431671128: a(n) FSUnixStore > 0xbfdc4608 I FSUnixStore(FSDiskStore)>nodeAt:ifPresent:ifAbsent: -1431671128: a(n) FSUnixStore > 0xbfdc4634 I FSUnixStore(FSStore)>exists: -1431671128: a(n) FSUnixStore > 0xbfdc4658 I FSFilesystem>exists: -1431671120: a(n) FSFilesystem > 0xbfdc467c I FSReference>exists -1431667420: a(n) FSReference > 0xbfdc469c I FSLocator>exists -1431671980: a(n) FSLocator > 0xbfdc46bc I FLHelper>hasConfDirectory -1431672032: a(n) FLHelper > 0xbfdc46dc I FLHelper>start -1431672032: a(n) FLHelper > 0xbfdc46fc I FLHelper class>start -1446907784: a(n) FLHelper class > 0xbfdc471c I FLHelper class>startUp -1446907784: a(n) FLHelper class > 0xbfdc4734 M FLHelper class(Behavior)>startUp: -1446907784: a(n) FLHelper class > 0xbfdc4760 M [] in SmalltalkImage>send:toClassesNamedIn:with: -1478292160: a(n) SmalltalkImage > 0xbfdc4788 I OrderedCollection>do: -1480202612: a(n) OrderedCollection > 0xbfdc47b0 I SmalltalkImage>send:toClassesNamedIn:with: -1478292160: a(n) SmalltalkImage > 0xbfdc47dc I SmalltalkImage>processStartUpList: -1478292160: a(n) SmalltalkImage > 0xbfdc4804 I [] in SmalltalkImage>snapshot:andQuit: -1478292160: a(n) SmalltalkImage > 0xbfdc4824 M BlockClosure>ensure: -1436539624: a(n) BlockClosure > 0xbfdc4848 I MorphicUIManager(UIManager)>boot:during: -1441995864: a(n) MorphicUIManager > 0xbfdc4878 I SmalltalkImage>snapshot:andQuit: -1478292160: a(n) SmalltalkImage > -1436547788 s SmalltalkImage>saveSession > -1436547696 s [] in ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: > -1436547604 s BlockClosure>ensure: > -1437443620 s CursorWithMask(Cursor)>showWhile: > -1437443732 s ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: > -1436547512 s ToggleMenuItemMorph(MenuItemMorph)>mouseUp: > -1436547420 s ToggleMenuItemMorph(MenuItemMorph)>handleMouseUp: > -1436547328 s MouseButtonEvent>sentTo: > -1436547236 s ToggleMenuItemMorph(Morph)>handleEvent: > -1436547144 s MorphicEventDispatcher>dispatchDefault:with: > -1436547052 s MorphicEventDispatcher>dispatchEvent:with: > -1436546960 s ToggleMenuItemMorph(Morph)>processEvent:using: > -1436546868 s MorphicEventDispatcher>dispatchDefault:with: > -1436546776 s MorphicEventDispatcher>dispatchEvent:with: > -1436546684 s MenuMorph(Morph)>processEvent:using: > -1436546592 s MenuMorph(Morph)>processEvent: > -1436546500 s MenuMorph>handleFocusEvent: > -1436546408 s [] in HandMorph>sendFocusEvent:to:clear: > -1436546316 s [] in PasteUpMorph>becomeActiveDuring: > -1437443244 s BlockClosure>on:do: > -1437444096 s PasteUpMorph>becomeActiveDuring: > -1437444216 s HandMorph>sendFocusEvent:to:clear: > -1436546224 s HandMorph>sendEvent:focus:clear: > -1437444332 s HandMorph>sendMouseEvent: > -1437444424 s HandMorph>handleEvent: > -1436546132 s HandMorph>processEvents > -1436546040 s [] in WorldState>doOneCycleNowFor: > -1436545948 s Array(SequenceableCollection)>do: > -1436545856 s WorldState>handsDo: > -1437444768 s WorldState>doOneCycleNowFor: > -1436545764 s WorldState>doOneCycleFor: > -1436545672 s PasteUpMorph>doOneCycle > -1441147720 s [] in Project class>spawnNewProcess > -1441147868 s [] in BlockClosure>newProcess > > Most recent primitives > value: > compare:with:collated: > compare:with:collated: > value: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > basicNew: > value:value: > at:put: > value:value: > at:put: > value:value: > at:put: > value:value: > at:put: > value:value: > at:put: > value:value: > at:put: > value:value: > at:put: > size > size > at: > compare:with:collated: > size > basicNew: > compare:with:collated: > new: > at:put: > basicNew > new: > basicNew: > species > basicNew: > replaceFrom:to:with:startingAt: > at:put: > size > + > basicNew: > species > basicNew: > replaceFrom:to:with:startingAt: > at:put: > basicNew: > species > basicNew: > replaceFrom:to:with:startingAt: > at:put: > basicNew: > species > basicNew: > replaceFrom:to:with:startingAt: > at:put: > basicNew: > species > basicNew: > replaceFrom:to:with:startingAt: > at:put: > basicNew: > species > basicNew: > replaceFrom:to:with:startingAt: > at:put: > basicNew: > species > basicNew: > replaceFrom:to:with:startingAt: > at:put: > basicNew: > size > species > basicNew: > replaceFrom:to:with:startingAt: > at:put: > basicNew > new: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > basicNew: > value:value: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > basicNew > size > = > size > at: > compare:with:collated: > size > basicNew: > at: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > basicNew > size > size > new: > size > at:put: > size > size > at: > basicNew > new: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > basicNew: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > basicNew > size > size > compare:with:collated: > basicNew: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > basicNew: > basicNew > value: > at:put: > size > new > value: > replaceFrom:to:with:startingAt: > value > at:put: > <= > * > + > value: > at: > replaceFrom:to:with:startingAt: > value > at:put: > value: > replaceFrom:to:with:startingAt: > value > at:put: > value: > replaceFrom:to:with:startingAt: > value > at:put: > value: > replaceFrom:to:with:startingAt: > value > at:put: > value: > replaceFrom:to:with:startingAt: > species > basicNew: > replaceFrom:to:with:startingAt: > basicNew > basicNew: > basicNew > findFirstInString:inSet:startingAt: > replaceFrom:to:with:startingAt: > lookupEntryIn:index: > > (Segmentation fault) >

April 7, 2012

Re: [Pharo-project] [ANN] NBOpenGL update

by StÃ©phane Ducasse

Igor thanks a lot. Did you define a stable version because like that we can publish it to the MetaReportForPharo14 and use the browser to load it. Stef On Apr 6, 2012, at 3:31 PM, Igor Stasenko wrote: > Hi there, > > for those, who interested, i updated a NBOpenGL configuration. > > Changes are: > > - updated GL API to most recent available (taken directly from opengl > specs). Now there is about 300 more methods to explore :) > - finally dealt with win32 support code and made it working again > - fixed the GLX function prefix , which should be 'glX' not 'glx' > > To load it in 1.4 use: > > Gofer new > squeaksource: 'NBOpenGL'; > package: 'ConfigurationOfNBOpenGL'; > load. > > > and then > > (ConfigurationOfNBOpenGL project version: '1.0.2') load > > I did not tested the update thoroughly.. so i would appreciate if > people will try it out and tell how it goes. > > > -- > Best regards, > Igor Stasenko. >

April 7, 2012

Re: [Pharo-project] How should we tag new issues

by StÃ©phane Ducasse

1.4 should get out. So only show stoppers On Apr 6, 2012, at 12:47 PM, Guillermo Polito wrote: > I have this issue: > > http://code.google.com/p/pharo/issues/detail?id=5584&thanks=5584&ts=1333709… > > I should not tag it as critical, but it is important to newcomers who are learning to use changesets and fileouts to have this working nicely :). > > how should we handle the new issues tagging? > > - critical/showstoppers for 1.4 > - non critical for 1.5 > > ? > > Guille

April 7, 2012

Re: [Pharo-project] Using Merlin in Web UI's

by StÃ©phane Ducasse

Yes there is. If I remember correctly there is a visitor or something like that that generates morphic or seaside. Stef On Apr 6, 2012, at 5:19 AM, HernÃ¡n Morales Durand wrote: > Hi all, > > Is there any support for using Merlin (a wizard library) with Seaside? (or any other web framework like Aida or Iliad) > Cheers, > > HernÃ¡n >

April 7, 2012

Re: [Pharo-project] using the system applied proxy in unix

by Mariano Martinez Peck

On Fri, Apr 6, 2012 at 11:30 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Apr 6, 2012, at 11:26 AM, Guillermo Polito wrote: > > > Hi, > > > > I have configured the proxy for the whole system in my ubuntu 11.10, but > pharo does not want to recognize it :). If i configure the proxy again in > my pharo image it works, but I don't want to have the configurations > duplicated... > > > The plugin that does the detection was nover portet to Linux and > Windows... so automatic proxy setting only works on the mac for now. > > Even worst, it only works in Carbon, not in cocoas vms :( > Marcus > > -- > Marcus Denker -- http://marcusdenker.de > > > -- Mariano http://marianopeck.wordpress.com

April 6, 2012

Re: [Pharo-project] Why do we have classOrganizer and BasicClassOrganizer?

by Guillermo Polito

On Fri, Apr 6, 2012 at 10:30 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 6 April 2012 20:07, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > > On Fri, Apr 6, 2012 at 6:59 PM, Igor Stasenko <siguctua(a)gmail.com> > wrote: > >> > >> On 6 April 2012 16:53, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > >> > BasicClassOrganizer has no users... Is it there for any purpose? > >> > > >> > What about joining them? > >> > > >> > >> Ehh... i was also looked at those classes couple years ago and > >> wondered why if its really worth > >> having so complex implementation to save few bytes of space.. > >> > >> I would rewrite this stuff and leave just a Categorizer with clean > >> protocol and structure: > > > > > > yes > > > >> - categorizer holds categories (order could be important, but i would > >> just keep it unspecified , i.e, > > > > > > yes. I was working in a simple version having #sort:, > #sortAlphabetically, > > #sortByAmmountOfElements > > > >> > >> instead > >> OrderedCollection ( categoryName -> {.. category items .. } ) > >> > >> I would use Dictionary > >> #categoryName -> Set(items) > > > > > > I'd like having a Category object there. > > > >> > >> > >> this class should serve basic operations like adding /removing and > >> queries: > >> - what is a categor(ies) of element (if element can be include only > >> into single category at once) > >> - what are category names > >> - what are elements of specific category.. > >> Period. > >> And it actually can serve as a general categorizer (not just for > >> classes/packages). > > > > > > but then we have to put the changes announcements/notifications in > another > > place > > > yes. of course. > usually operations are logged by separate entity than in place where > it actually happens. > you recording some operation over some model, and model don't > necessary needs to know > that you recording, isn't? > I'm with you :), was just remarking one implication of the change. And thinking that way makes the change much more aggressive :P. But I know, step by step... > > >> > >> > >> The way how BasicClassOrganizer using inheritance is abuse.. > >> since it extends a clean concept (Categorizer) with unrelated stuff, > >> like classComment and commentStamp. > > > > > > Ok, you are making me open an issue to move those to class :). 1.5? > > > >> > >> Class organizer, should instead delegate, or even better, Class > >> should use two different fields for categories and class comment.. > >> but not mixing everything into one pile of mess. > >> > >> > Guille > >> > >> -- > >> Best regards, > >> Igor Stasenko. > >> > > > > > > -- > Best regards, > Igor Stasenko. > >

April 6, 2012

Re: [Pharo-project] Why do we have classOrganizer and BasicClassOrganizer?

by Igor Stasenko

On 6 April 2012 20:07, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > On Fri, Apr 6, 2012 at 6:59 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> On 6 April 2012 16:53, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> > BasicClassOrganizer has no users...Â Is it there for any purpose? >> > >> > What about joining them? >> > >> >> Ehh... i was also looked at those classes couple years ago and >> wondered why if its really worth >> having so complex implementation to save few bytes of space.. >> >> I would rewrite this stuff and leave just a Categorizer with clean >> protocol and structure: > > > yes > >> Â - categorizer holds categories (order could be important, but i would >> just keep it unspecified , i.e, > > > yes.Â I was working in a simple version having #sort:, #sortAlphabetically, > #sortByAmmountOfElements > >> >> instead >> Â OrderedCollection ( categoryName -> {.. category items .. } ) >> >> I would use Dictionary >> #categoryName -> Set(items) > > > I'd like having a Category object there. > >> >> >> this class should serve basic operations like adding /removing and >> queries: >> Â - what is a categor(ies) of element (if element can be include only >> into single category at once) >> Â - what are category names >> Â - what are elements of specific category.. >> Period. >> And it actually can serve as a general categorizer (not just for >> classes/packages). > > > but then we have to put the changes announcements/notifications in another > place > yes. of course. usually operations are logged by separate entity than in place where it actually happens. you recording some operation over some model, and model don't necessary needs to know that you recording, isn't? >> >> >> The way how Â BasicClassOrganizer using inheritance is abuse.. >> since it extends a clean concept (Categorizer) with unrelated stuff, >> like classComment and commentStamp. > > > Ok, you are making me open an issue to move those to class :). 1.5? > >> >> Class organizer, should instead delegate, Â or even better, Class >> should use two different fields for categories and class comment.. >> but not mixing everything into one pile of mess. >> >> > Guille >> >> -- >> Best regards, >> Igor Stasenko. >> > -- Best regards, Igor Stasenko.

April 6, 2012

Re: [Pharo-project] Docking windows

by Mark Smith

:) Very cool! On 6 Apr 2012, at 11:52, Guillermo Polito wrote: > I wanted docking windows, so I did a little change over the MorphFrameGhost to support it. > > If anyone wants to try, filein the attached the changeset and then evaluate: > > UITheme currentSettings fastDragging: true. > > Guille > <docking windows.cs>

April 6, 2012

Re: [Pharo-project] Vm on iOS with Xcode 4.3

by phil＠highoctane.be

Oh great news! Tomorrow will be Pharo iOS day. Le 6 avr. 2012 17:54, "Esteban Lorenzano" <estebanlm(a)gmail.com> a Ã©crit : > Hi, > > On Apr 6, 2012, at 10:51 AM, phil(a)highoctane.be wrote: > > I am still unable to get this to work. > > latest nightly build from cmake is able to build valid xcode projects > again [1]. > Some adjusts are needed to actually build, but it is almost there (I will > take care about that this days) > > Also I see a jenkins build for OSX but not for iOS. > > Yeah, and I want to have one, but it will take time (and time is tyrant, > you know). > > XCode 4.3 will open old xcode projects so posting a full set of files that > work out of cmake (ie a fully made build/ folder) would help a lot. > > Would you be able to ship me such a set of files? > > you already have them: clone of my repository [2] or blessed [3] and > install latest ConfigurationOfCog > > best, > Esteban > > [1] > http://www.cmake.org/files/dev/cmake-2.8.7.20120405-gd2c9c-Darwin64-univers… > [2] https://gitorious.org/~estebanlm/cogvm/cog-osx > [3] https://gitorious.org/cogvm/blessed > > > >

April 6, 2012

Re: [Pharo-project] cog and libSqueakSSL.so

by Sven Van Caekenberghe

On 06 Apr 2012, at 15:15, Igor Stasenko wrote: > Yes, Camillo just added SSL plugin into build, but its not yet even checked if it functional or not. No problem, I am all for pushing new stuff. But it is confusing if people start downloading it as 'released'. There should be a development and release version of the vm's as well, IMHO. Even more than for an image, people need a stable vm to depend on. >> Maybe someone can suggest a link to an older pharo linux vm. The archive that I am using looks like this: >> >> $ ls -l cog-vm.zip >> -rw-rw-r-- 1 ubuntu ubuntu 611334 2012-03-01 11:55 cog-vm.zip >> >> $ md5sum cog-vm.zip >> 479ba1a66a91b10bdc2374a661771814 cog-vm.zip >> >> I could publish mine somewhere if that helps. >> >> Sven >> >

April 6, 2012