- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Crash on saving with Monticello

by Alexandre Bergel

> Alexandre, so you changed from: > > primMakeUUID > <primitive: 'primitiveMakeUUID' module: 'UUIDPlugin'> > UUIDGenerator default generateBytes: self forVersion: 4 > > to: > > primMakeUUID > UUIDGenerator default generateBytes: self forVersion: 4. > > ? Yes. I was able to save and load from Monticello. > What about changing to: > > primMakeUUID > self isOSSafeForUUID > ifTrue: [ ^ self internalPrimitiveMakeUUID ] > ifFalse: [^ UUIDGenerator default generateBytes: self forVersion: 4]. > > > isOSSafeForUUID > "it would be great being able to check wether the OS is 64 bits or not, but I don't know how to ask that from the image" > ^ Smalltalk os isUnix not > > internalPrimitiveMakeUUID > <primitive: 'primitiveMakeUUID' module: 'UUIDPlugin'> I haven't found myself very close to the UUID problem and I do not have a global picture of the problem. If other agree, then I am ok. Alexandre > Then....when this is really fixed, we remove all this crap. > Of you agree, I open a ticket. > > Cheers > > mariano > > > > Cheers, > Alexandre > > > On 28 Dec 2010, at 10:09, Mariano Martinez Peck wrote: > > > > > > > On Tue, Dec 28, 2010 at 2:00 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > Hi! > > > > Several of my students experience a crash of Pharo when saving with Monticello. They all use linux. I can ask for more detailed description. > > Are we the only one to experience this? > > > > > > yes, probably the UUID known problem. Just renaming / removing the plugin may work. > > Are they in Ubuntu/debian? > > > > Please let us know if we should do this for the PharoOneClick image. > > > > cheers > > > > mariano > > > > Cheers, > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 3, 2011

Re: [Pharo-project] Crash on saving with Monticello

by Mariano Martinez Peck

On Mon, Jan 3, 2011 at 3:25 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Hi! > > Sorry for the late answer. The student is now in my office and there is > indeed a problem. > UUIDPlugin is not present on his harddisk. Maybe built in the VM. > > I found the class UUID and remove the call to the primitive. It works. > Strange problem. Shall I report it in codegoogle? > yes, please. We need to aboid this somehow Alexandre, so you changed from: primMakeUUID <primitive: 'primitiveMakeUUID' module: 'UUIDPlugin'> UUIDGenerator default generateBytes: self forVersion: 4 to: primMakeUUID UUIDGenerator default generateBytes: self forVersion: 4. ? What about changing to: primMakeUUID self isOSSafeForUUID ifTrue: [ ^ self internalPrimitiveMakeUUID ] ifFalse: [^ UUIDGenerator default generateBytes: self forVersion: 4]. isOSSafeForUUID "it would be great being able to check wether the OS is 64 bits or not, but I don't know how to ask that from the image" ^ Smalltalk os isUnix not internalPrimitiveMakeUUID <primitive: 'primitiveMakeUUID' module: 'UUIDPlugin'> Then....when this is really fixed, we remove all this crap. Of you agree, I open a ticket. Cheers mariano > Cheers, > Alexandre > > > On 28 Dec 2010, at 10:09, Mariano Martinez Peck wrote: > > > > > > > On Tue, Dec 28, 2010 at 2:00 PM, Alexandre Bergel <alexandre(a)bergel.eu> > wrote: > > Hi! > > > > Several of my students experience a crash of Pharo when saving with > Monticello. They all use linux. I can ask for more detailed description. > > Are we the only one to experience this? > > > > > > yes, probably the UUID known problem. Just renaming / removing the plugin > may work. > > Are they in Ubuntu/debian? > > > > Please let us know if we should do this for the PharoOneClick image. > > > > cheers > > > > mariano > > > > Cheers, > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > >

Jan. 3, 2011

Re: [Pharo-project] Issue 3499 in pharo: FixUnderscores (package & instructions) out of date

by pharo＠googlecode.com

Comment #2 on issue 3499 by sean.p.denigris: FixUnderscores (package & instructions) out of date http://code.google.com/p/pharo/issues/detail?id=3499 "I do not understand why you want to integrate 18 in the trunk since in 1.2 there is 20." Just a mistake. I meant "update to the latest version", and thought 18 was it.

Jan. 3, 2011

Re: [Pharo-project] IRC meeting next Tuesday, January 4, at ...?

by Adrian Lienhard

I just figured that I also can't make it tomorrow at 20:00 (I can be online 2 hours later, though). Anyway, I suggest that everybody who is interested to discuss and sync meets at 20:00 and it would be nice if somebody could write a short summary, which we can post to the mailing list and the website. BTW, the channel is #pharo-project on irc.freenode.net. If you don't have an IRC client you can browse to http://webchat.freenode.net/?channels=pharo-project Time: http://www.timeanddate.com/counters/customcounter.html?day=4&month=1&year=2… Cheers, Adrian On Jan 3, 2011, at 09:15 , StÃ©phane Ducasse wrote: > Thanks for the call adrian. I will be travelling until 16h (it was not planned when I proposed that dat) but there is no problem, > Stef > On Jan 2, 2011, at 10:34 PM, Adrian Lienhard wrote: > >> Hi all, >> >> During the last meeting [1] we decided to do the next one on January 4 but we didn't decide when to start. >> >> The previous meeting started at 20:00 CET/UTC/GMT+1, which may not be optimal for people in other time zones. If somebody likes to suggest another time, please let us know soon! >> >> Cheers, >> Adrian >> >> [1] http://pharo-project.org/news?article=irc-meeting-notes > >

Jan. 3, 2011

Re: [Pharo-project] Crash on saving with Monticello

by David T. Lewis

On Mon, Jan 03, 2011 at 09:14:47PM +0100, Philippe Marschall wrote: > On 03.01.2011 16:42, David T. Lewis wrote: > > On Mon, Jan 03, 2011 at 03:57:07PM +0100, Philippe Marschall wrote: > >> On 01/03/2011 03:25 PM, Alexandre Bergel wrote: > >>> Hi! > >>> > >>> Sorry for the late answer. The student is now in my office and there is indeed a problem. > >>> UUIDPlugin is not present on his harddisk. Maybe built in the VM. > >>> > >>> I found the class UUID and remove the call to the primitive. It works. Strange problem. Shall I report it in codegoogle? > >> > >> Has been known for two years, shouldn't happen, nobody cares. > >> > > > > Huh ?!?!? What do you mean "nobody cares"? > > Nodby cares enough to get to the bottom of it and fix it once and for > all. And yes, that includes me. It's just an observation. So if this is > really critical for somebody then he'll have to fix it himself. > Reporting the same bug again won't make a difference. That's just how > open source is. > > Cheers > Philippe > Yep :) But I do want to make it clear that it seems the bug is not in the plugin, it is in the libuuid implementations. We've all been trying to find workarounds, but unfortunately not with much success. For a while we could work around it by compiling the plugin internally (which somehow prevents the bug from being exposed), but now we have some 64-bit Linux distros that accidentally left the 32-bit libuuid out of the distro, which prevents the VM from running if the plugin was compiled internally. I'm sure it has been fixed in up to date distros, but now we have one set of Linux users with buggy libuuid libraries, and another set of Linux users with missing 32-bit libuuid libraries, so somebody is going to get screwed either way now :-/ I'm sure there must be some way to fix this that we're all missing, so if anyone wants to look at it with a fresh set of eyes that would be great. Dave

Jan. 3, 2011

Re: [Pharo-project] Issue 3499 in pharo: FixUnderscores (package & instructions) out of date

by pharo＠googlecode.com

Updates: Status: accepted Comment #1 on issue 3499 by stephane.ducasse: FixUnderscores (package & instructions) out of date http://code.google.com/p/pharo/issues/detail?id=3499 We should not maintain documentation for 1.0 users when we are not even able to have a decent documentation. So upgrading the documentation to the current version is the only way. Now I do not understand why you want to integrate 18 in the trunk since in 1.2 there is 20.

Jan. 3, 2011

Re: [Pharo-project] Issue 3504 in pharo: MethodContext>>numArgs

by pharo＠googlecode.com

Updates: Status: closed Comment #1 on issue 3504 by stephane.ducasse: MethodContext>>numArgs http://code.google.com/p/pharo/issues/detail?id=3504 in 12293

Jan. 3, 2011

Re: [Pharo-project] new Cog VMs

by StÃ©phane Ducasse

Thanks http://code.google.com/p/pharo/issues/detail?id=3504 Stef On Jan 3, 2011, at 8:38 PM, Eliot Miranda wrote: > The MethodContext>>numArgs is I guess to be expected because there's no implementation so far. Find attached. > > 'From Pharo-1.1.1-- of 12 September 2010 [Latest update: #11414] on 2 January 2011 at 2:23:32 pm'! > > !MethodContext methodsFor: 'accessing' stamp: 'eem 1/2/2011 14:23'! > numArgs > "Answer the number of arguments required to evaluate this method or block." > > ^closureOrNil ifNil: [method numArgs] ifNotNil: [closureOrNil numArgs]! ! > > > On Sun, Jan 2, 2011 at 2:49 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi Eliot. Running: > > - Mac OS > - VM r2340 > - PharoCore 1.2 12288 > > Running all tests I got this DNU. > It is reproducable running the test testClosureRestart which seems to pass well in previous VMs. > > Cheers > > Mariano > > THERE_BE_DRAGONS_HERE > MessageNotUnderstood: MethodContext>>numArgs > 2 January 2011 11:38:31 am > > VM: Mac OS - intel - 1065 - Croquet Closure Cog VM [CoInterpreter VMMaker-oscog.41] Croquet Cog 3.0.0 > Image: Pharo1.2beta [Latest update: #12288] > > SecurityManager state: > Restricted: false > FileAccess: true > SocketAccess: true > Working Dir /Users/mariano/Pharo/imagenes/PharoCore-1.2beta-12283 > Trusted Dir /foobar/tooBar/forSqueak/bogus/ > Untrusted Dir /Users/mariano/Library/Preferences/Croquet/Internet/Untrusted > > MethodContext(Object)>>doesNotUnderstand: #numArgs > Receiver: [| b | > self assert: 10 == a. > self assert: nil == b. > b := a + 20. > firstTimeThrough > ifT...etc... > Arguments and temporary variables: > t1: numArgs > t2: nil > t3: nil > Receiver's instance variables: > sender: nil > pc: nil > stackp: 3 > method: (MethodContextTest>>#privRestartBlockTest "a CompiledMethod(700186624)"...etc... > closureOrNil: [| b | > self assert: 10 == a. > self assert: nil == b. > b := a + 20...etc... > receiver: MethodContextTest>>#testClosureRestart > > > > --- The full stack --- > MethodContext(Object)>>doesNotUnderstand: #numArgs > ------------------------------------------------------------ > > > > > On Sun, Jan 2, 2011 at 8:52 AM, Philippe Marschall <kustos(a)gmx.net> wrote: > On 01.01.2011 21:38, Eliot Miranda wrote: > > Hi All, > > > > there are new versions of both the SimpleStackBasedCogit and the > > StackToRegisterMappingCogit Cog VMs in VM.r2337/ > > <http://www.mirandabanda.org/files/Cog/VM/VM.r2337/> & VM.r2338/ > > <http://www.mirandabanda.org/files/Cog/VM/VM.r2338/> respectively. > > These contain fixes for another bad pc mapping bug that could cause > > hard crashes when jitting on a backward branch in a looping interpreted > > method. If you're trying to reproduce Cog crashes please upgrade to one > > of tthese two VMs. > > > > TIA > > and happy new 2011, P.S. according to an FBF > > RT @dpp RT @giuliodeluise 2011 is a prime number & the sum of 11 > > consecutive prime numbers: 2011=157+163+167+173+179+181+191+193+197+199+211 > > Crashes right at start up: > > Segmentation fault > > > > Smalltalk stack dump: > 0xff8aafb4 M Error class(Exception class)>handles: -1246542340: a(n) > Error class > 0xff8aafdc M MethodContext(ContextPart)>handleSignal: -1220670568: a(n) > MethodContext > 0xff8aaffc M MethodContext(ContextPart)>handleSignal: -1216945468: a(n) > MethodContext > 0xff8ab020 I UnhandledError(Exception)>signal -1216945236: a(n) > UnhandledError > 0xff8ab040 I UnhandledError class>signalForException: -1246541380: a(n) > UnhandledError class > 0xff8ab064 I MessageNotUnderstood(Error)>defaultAction -1216945688: a(n) > MessageNotUnderstood > 0xff8ab084 I MessageNotUnderstood>defaultAction -1216945688: a(n) > MessageNotUnderstood > 0xff8ab0a8 I UndefinedObject>handleSignal: -1247481852: a(n) UndefinedObject > 0xff8ab0cc I MessageNotUnderstood(Exception)>pass -1216945688: a(n) > MessageNotUnderstood > 0xff8ab0f8 I [] in PasteUpMorph>becomeActiveDuring: -1245846436: a(n) > PasteUpMorph > 0xff8ab11c I BlockClosure>valueWithPossibleArgs: -1221000224: a(n) > BlockClosure > 0xff8ab13c M [] in MethodContext(ContextPart)>handleSignal: -1220670568: > a(n) MethodContext > 0xff8ab15c M BlockClosure>ensure: -1216945284: a(n) BlockClosure > 0xff8ab17c M MethodContext(ContextPart)>handleSignal: -1220670568: a(n) > MethodContext > 0xff8ab1a4 I MethodContext(ContextPart)>handleSignal: -1216945468: a(n) > MethodContext > 0xff8ab1c8 I MessageNotUnderstood(Exception)>signal -1216945688: a(n) > MessageNotUnderstood > 0xff8ab1f0 I ProcessorScheduler(Object)>doesNotUnderstand: >= > -1247476532: a(n) ProcessorScheduler > 0xff8ab210 M Process>priority: -1216945752: a(n) Process > 0xff8ab238 I BlockClosure>forkAt: -1216945972: a(n) BlockClosure > 0xff8ab25c I > InputEventPollingFetcher(InputEventFetcher)>installEventLoop > -1246030580: a(n) InputEventPollingFetcher > 0xff8ab280 I InputEventPollingFetcher(InputEventFetcher)>startUp > -1246030580: a(n) InputEventPollingFetcher > 0xff8ab2a0 I InputEventFetcher class>startUp -1246046280: a(n) > InputEventFetcher class > 0xff8ab2b8 M InputEventFetcher class(Behavior)>startUp: -1246046280: > a(n) InputEventFetcher class > 0xff8ab2e0 M [] in SmalltalkImage>send:toClassesNamedIn:with: > -1242015264: a(n) SmalltalkImage > 0xff8ab2fc M BlockClosure>on:do: -1216946688: a(n) BlockClosure > 0xff8ab32c M [] in SmalltalkImage>send:toClassesNamedIn:with: > -1242015264: a(n) SmalltalkImage > 0xff8ab354 I OrderedCollection>do: -1241999736: a(n) OrderedCollection > 0xff8ab37c I SmalltalkImage>send:toClassesNamedIn:with: -1242015264: > a(n) SmalltalkImage > 0xff8ab3a8 I SmalltalkImage>processStartUpList: -1242015264: a(n) > SmalltalkImage > 0xff8ab3d4 I SmalltalkImage>snapshot:andQuit:embedded: -1242015264: a(n) > SmalltalkImage > -1220672224 s SmalltalkImage>snapshot:andQuit: > -1220672132 s WorldState class>saveAndQuit > -1220672040 s [] in ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: > -1220671948 s BlockClosure>ensure: > -1220999860 s CursorWithMask(Cursor)>showWhile: > -1220999972 s ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: > -1220671856 s ToggleMenuItemMorph(MenuItemMorph)>mouseUp: > -1220671764 s ToggleMenuItemMorph(MenuItemMorph)>handleMouseUp: > -1220671672 s MouseButtonEvent>sentTo: > -1220671580 s ToggleMenuItemMorph(Morph)>handleEvent: > -1220671488 s MorphicEventDispatcher>dispatchDefault:with: > -1220671396 s MorphicEventDispatcher>dispatchEvent:with: > -1220671304 s ToggleMenuItemMorph(Morph)>processEvent:using: > -1220671212 s MorphicEventDispatcher>dispatchDefault:with: > -1220671120 s MorphicEventDispatcher>dispatchEvent:with: > -1220671028 s MenuMorph(Morph)>processEvent:using: > -1220670936 s MenuMorph(Morph)>processEvent: > -1220670844 s MenuMorph>handleFocusEvent: > -1220670752 s [] in HandMorph>sendFocusEvent:to:clear: > -1220670660 s [] in PasteUpMorph>becomeActiveDuring: > -1220670568 s BlockClosure>on:do: > -1221000336 s PasteUpMorph>becomeActiveDuring: > -1221000456 s HandMorph>sendFocusEvent:to:clear: > -1220670476 s HandMorph>sendEvent:focus:clear: > -1221000572 s HandMorph>sendMouseEvent: > -1221000664 s HandMorph>handleEvent: > -1220670384 s HandMorph>processEvents > -1220670292 s [] in WorldState>doOneCycleNowFor: > -1220670200 s Array(SequenceableCollection)>do: > -1220670108 s WorldState>handsDo: > -1221001008 s WorldState>doOneCycleNowFor: > -1220670016 s WorldState>doOneCycleFor: > -1220669924 s PasteUpMorph>doOneCycle > -1221589100 s [] in Project class>spawnNewProcess > -1221602884 s [] in BlockClosure>newProcess > > Most recent primitives > basicNew > size > at: > basicNew: > decompress:fromByteArray:at: > beCursorWithMask: > vmParameterAt:put: > vmParameterAt:put: > setGCBiasToGrowGCLimit: > setGCBiasToGrow: > ensure: > valueNoContextSwitch > wait > value > specialObjectsArray > new: > at:put: > value > signal > basicNew > new: > at: > value: > basicIdentityHash > on:do: > value > perform:with: > millisecondClockValue > signal > value: > size > size > bitShift: > \\ > \\ > \\ > \\ > \\ > perform:with: > shallowCopy > subclasses > new: > new: > new: > // > value: > value: > value: > = > = > value: > value: > at:put: > value: > at:put: > addAll: > - > + > + > + > size > at: > do: > do: > value: > getSystemAttribute: > compare:with:collated: > value: > value: > platformName > = > = > value: > value: > getSystemAttribute: > compare:with:collated: > determineActivePlatformStartingAt: > determineActivePlatformStartingAt: > basicNew > value: > value: > value: > value: > perform:with: > actualScreenSize > species > species > supportsDisplayDepth: > new: > basicNew > beDisplay > value: > perform:with: > isMemberOf: > value: > perform:with: > basicNew > critical: > critical: > wait > wait > specialObjectsArray > species > new: > replaceFrom:to:with:startingAt: > specialObjectsArray > at:put: > at:put: > primSetInputSemaphore: > suspend > findNextUnwindContextUpTo: > value: > bottomContext > objectAt: > basicNew: > basicNew > basicNew > findNextHandlerContextStarting > tempAt: > nextHandlerContext > handleSignal: > isKindOf: > tempAt:put: > tempAt:put: > tempAt:put: > valueWithArguments: > findNextHandlerContextStarting > basicNew > findNextHandlerContextStarting > tempAt: > findNextHandlerContextStarting > tempAt: > Abgebrochen > > Cheers > Philippe > > > > > <MethodContext-numArgs.st>

Jan. 3, 2011

[Pharo-project] Issue 3504 in pharo: MethodContext>>numArgs

by pharo＠googlecode.com

Status: Fixed Owner: stephane.ducasse Labels: Milestone-1.2 New issue 3504 by stephane.ducasse: MethodContext>>numArgs http://code.google.com/p/pharo/issues/detail?id=3504 MethodContext>>numArgs "Answer the number of arguments required to evaluate this method or block." ^closureOrNil ifNil: [method numArgs] ifNotNil: [closureOrNil numArgs]

Jan. 3, 2011

Re: [Pharo-project] next steps for pharo

by StÃ©phane Ducasse

I meant the coolest documenter :) Stef >> The coolest programmer of the month ;) > > Take care, sometimes the "coolest programmer" is the > one who is not interested in writing documentation. > > Sometimes people think they are cool when they > win the IOCCC contest [1] or find neat coding tricks > that other people do not understand. > > Following conformance rules, writing clean code or > documenting is often seen as "boring task" but necessary > to grow into professional shared development. > > So we have to find a way to turn "boring" into "simple & fun". > > Bye > T. > > [1] http://de.wikipedia.org/wiki/International_Obfuscated_C_Code_Contest > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de >

Jan. 3, 2011