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

[Pharo-project] Suspending process fix
by Igor Stasenko April 28, 2009

April 28, 2009

Hello, i trying to provide a fix to the issue http://bugs.squeak.org/view.php?id=6822 what is needed to make following code work w/o error: |sema proc | sema := Semaphore new. proc := [ sema wait. self error: 'should not be there' ] fork. Processor yield. proc suspend. proc resume. The problem here, is that once you issue a #suspend on a process it puts nil to its myList ivar, ignoring the fact that it could be waiting on semaphore. This leads to disconnecting the process from semaphore, and any subsequent 'sema signal' will be simply lost: suspend | oldList | <primitive: 88> "primitive will fail, if receiver is not active process, which is just our case" myList ifNil:[^nil]. oldList := myList. myList := nil. oldList remove: self ifAbsent:[]. ^oldList the possible fix would be: - add an instance variable to Process, say 'semaphore'. - fix the #suspend to following: suspend | oldList | <primitive: 88> "primitive will fail, if receiver is not active process, which is just our case" myList ifNil:[^nil]. oldList := myList. myList := nil. oldList remove: self ifAbsent:[]. oldList isKindOf: Semaphore ifTrue: [ semaphore := oldList ]. ^oldList - then, in the #resume resume suspendedContext ifNil: [^ self primitiveFailed]. semaphore ifNotNil: [ semaphore resumeWaiting: self. semaphore := nil. ^ self. ] ^ self primitiveResume and Semaphore>>resumeWaiting: aProcess excessSignals>0 ifTrue: [excessSignals := excessSignals-1. aProcess primitiveResume. "resume immediately" ] ifFalse: [self addLastLink: aProcess] ---------- An attached file is the changeset which makes following test to work w/o failure: |sema proc bool | bool := true. sema := Semaphore new. proc := [ sema wait. bool ifTrue: [self error: 'should not be there']. Transcript show: 'semaphore signaled' ] fork. Processor yield. proc newSuspend. proc newResume. self assert: (sema last == proc). bool := false. sema signal. P.S. i didn't checked how this fix will affect other things around processes, like mentioned by Mike: Note that Process>>signalException: (as of in Squeak 3.8, it may be fixed in later versions?) relies on this broken behaviour. -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] Random failures with Linux VM
by Michael Rueger April 27, 2009

April 27, 2009

Hi all, while trying to update a 10281 on the closure (exupery) Linux VM I'm running into random failures like DNUs, failed network access etc. I'm running ubuntu in VirtualBox. Has anybody seen anything similar? Maybe I should try to build a "normal" Linux VM, just to check... Michael

5 9

[Pharo-project] Recent changes to Pharo
by Scott Gibson April 27, 2009

April 27, 2009

I have noticed with the newer releases (pharo0.1-10277dev09.04.2 and pharo0.1-10279dev09.04.3) there, which seemed to me, to be fixes/ improvements that were lost from the earlier (Pharo0.1Core-10268cl and pharo0.1-10268dev09.04.1) releases. These following occur for both the Mac and Windows platforms: #1) Running "(1 to: 100) do: [:each | Transcript show: each; cr]" is near instantaneous in the Transcript window compared to the more recent releases. #2) For the process "the UI process" in the Process Browser - when "the UI process" is selected processes actually show up but not in the more recent releases. #3) The debugger buttons are once again centered and squished in the middle of the debugging window. Is this actually now the norm? I am not sure exactly what is expected for these in Pharo's current state but it seemed that perhaps some fixes had reverted and I should submit issues for them. Was version 10268 the anomaly or are these actual issues? Thanks! Scott

3 3

[Pharo-project] fun question and answer
by StÃ©phane Ducasse April 27, 2009

April 27, 2009

Hi guys I want to print the name of a classVar and its value. So I tried something like Processor class classVarNames do: [:each | Transcript show: each ; show: each value ; cr] the solution.... Processor class classVarNames do: [:each | Transcript show: each ; show: (Compiler evaluate: each for: Processor logged: false) printString ; cr]

2 2

[Pharo-project] Clipboard problems on 10289
by Janko MivÅ¡ek April 27, 2009

April 27, 2009

There is also a clipboard problem with pharo on my machine. I cannot copy from VW and paste to Pharo, clipboard buffer seems to be empty. But I can paste the other direction, from Pharo to VW. If I copy from some other source like this text from Thunderbird, it copies but with cr or something appended at the end (a character like [] ). I'm on openSuse 11.1 on KDE. Best regards Janko -- Janko MivÅ¡ek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565

4 11

[Pharo-project] Which mysql client for Pharo?
by Hilaire Fernandes April 27, 2009

April 27, 2009

Hello people, I am in need of a mysql package to fetch data and to inject it in a Magma database. Which mysql client could one suggest me to use with Pharo? I remember Lukas referring about some issue with the mysql client he was using. Hilaire -- http://blog.ofset.org/hilaire

3 4

[Pharo-project] About 4.0.1
by StÃ©phane Ducasse April 27, 2009

April 27, 2009

Hi john doubleclicking on a image does not launch anymore a new VM but try to load the image in a running one. is it coming from me? Stef

3 4

[Pharo-project] Issue 751: "the UI process" does not show any processes in the Process Browser
by StÃ©phane Ducasse April 27, 2009

April 27, 2009

http://code.google.com/p/pharo/issues/detail?id=751

1 0

[Pharo-project] Networking problems
by Michael Rueger April 27, 2009

April 27, 2009

Hi all, a quick survey on the networking problems: - which platform - debug logs - issue tracker entries I've seen a few reports on the mailing list but mostly mentioned in emails about a different subject, so a bit more information would help to track down the problem(s) :-) Thanks Michael

3 6

[Pharo-project] Mac clipboard
by Michael Rueger April 27, 2009

April 27, 2009

Hi all, after updating to 10293 and installing the sensor, copy and paste work for me using the 4.1 VM. Michael

2 2