March 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Vm-dev] We need help from VM experts. Re: Freeze after Morph& nbsp; & nbsp; & nbsp; & nbsp; Activity
by Eliot Miranda March 9, 2017

March 9, 2017

Hi Juan, Hi All, On Mon, Mar 6, 2017 at 6:06 AM, Juan Vuletich <JuanVuletich(a)zoho.com> wrote: > > I finally understood what was happening. The problem with is primitive 136: > > primSignal: aSemaphore atMilliseconds: aSmallInteger > "Signal the semaphore when the millisecond clock reaches the value of > the second argument. Fail if the first argument is neither a Semaphore nor > nil. Essential. See Object documentation whatIsAPrimitive." > <primitive: 136> > ^self primitiveFailed > Yes, but primitive 136 *should not be used* :-). You should use primitive 242: primSignal: aSemaphore atUTCMicroseconds: anInteger "Signal the semaphore when the UTC microsecond clock reaches the value of the second argument. Fail if the first argument is neither a Semaphore nor nil, or if the second argument is not an integer. Essential. See Object documentation whatIsAPrimitive." <primitive: 242> ^self primitiveFailed The use of the UTC microsecond count eliminates any and all wrapping issues for about 50,000 years [puhleaze Mr Pruitt can you try and do your bit to make it possible that we'll make it that far. hic. ed.]. The old primitive 136 primSignal:atMilliseconds: is subject to wrapping problems. I see that primSignal:atMilliseconds: is still used in Squeak 5.x but only to turn off signaling: Delay class>>shutDown "Suspend the active delay, if any, before snapshotting. It will be reactived when the snapshot is resumed." "Details: This prevents a timer interrupt from waking up the active delay in the midst snapshoting, since the active delay will be restarted when resuming the snapshot and we don't want to process the delay twice." AccessProtect wait. self primSignal: nil atMilliseconds: 0. self saveResumptionTimes. DelaySuspended := true. Delay class>>stopTimerInterruptWatcher "Reset the class variables that keep track of active Delays and re-start the timer interrupt watcher process. Any currently scheduled delays are forgotten." "Delay startTimerInterruptWatcher" self primSignal: nil atMilliseconds: 0. TimingSemaphore ifNotNil:[TimingSemaphore terminateProcess]. I will change this now. HTH > If the requested tick is already in the past, all the VMs except for > Spur-64 will signal the semaphore anyway. Spur-64 won't. Taking care of > this in the Cuis image was easy enough. > > Squeak seems not to be affected because it uses a newer primitive, that > takes the large integer microsecond ticker, that might have the older > behavior (signaling anyway). I'm not really sure, and maybe someone could > check the primitive behavior and the corresponding assumptions in Squeak. > > Older Squeak images are not affected, as they are all 32-bit. So maybe > there's no action required. In any case, making the behavior consistent > across VMs and in both primitives would be nice. > > Cheers, > > On 3/3/2017 3:55 PM, Juan Vuletich wrote: > > > > Hi Folks, > > Today, I was able to get closer to the origin of the problem. The problem > is when Morphic tries to do a Delay (inter-cycle-pause) of 1 or two > milliseconds. (Usually they are quite larger, and the problem does not > appear). With the 64-bit VM, sometimes very short delays hang the complete > system. I don't know why, but this: > > waitDelay _ Delay forMilliseconds: 50. > [ true ] whileTrue: [ > 1000 atRandom print. > waitDelay setDelay: 1; wait ]. > > is enough to hang Cuis in a short time. When trying to reproduce the > problem in Squeak I had mixed results. It doesn't seem to hang there, but > if I let this run for a couple of minutes and then try to halt with alt-. , > then the hang occurs, and Squeak becomes irresponsibe. As a workaround, in > Cuis in the inter cycle pause, I'm avoiding very short delays. > > I'm not sure if the bug is in the VM, in the image, or both, but it is > still there, and it also affects Squeak. I haven't tried it, but Pharo > might also have the problem (if not, it can show a possible solution). > > BTW, Bert, I guess Squeak never does short delays in #interCyclePause: ... > > Thanks, > > On 2/6/2017 12:28 PM, Bert Freudenberg wrote: > > > > Yes, I tried with Spur64. Have not seen it freeze yet on Mac in Squeak, > but we possibly have not replicated the test well enough yet. > > It *did* freeze in Cuis Spur64 on Mac too. > > - Bert - > > On Mon, Feb 6, 2017 at 2:08 PM, Juan Vuletich <juanvuletich(a)zoho.com> > wrote: > >> >> Were you usig Spur64? On Debian it does not freeze with CogV3 or Spur32. >> Only with Spur64. >> >> Thanks, >> Juan >> >> Sent using Zoho Mail <https://www.zoho.com/mail/> >> >> >> ---- On Mon, 06 Feb 2017 09:19:48 -0300 * bert(a)freudenbergs.de >> <bert(a)freudenbergs.de> * wrote ---- >> >> On Mon, Feb 6, 2017 at 3:15 AM, David T. Lewis <lewis(a)mail.msen.com> >> wrote: >> >> It would be interesting to try reproducing this in a Squeak image, but I >> have not quite figured out how to make the Tokenish example work in >> Squeak. >> >> >> See attachment. Did not freeze on Mac with 10 Tokenish jumping. >> - Bert - >> >> >> >> > > > -- > Juan Vuletichwww.cuis-smalltalk.orghttps://github.com/Cuis-Smalltalk/Cuis-Smallt… > @JuanVuletich > > > > -- > Juan Vuletichwww.cuis-smalltalk.orghttps://github.com/Cuis-Smalltalk/Cuis-Smallt… > @JuanVuletich > > > -- _,,,^..^,,,_ best, Eliot

1 0

implementors followed by rename method -> DNU
by stepharong March 9, 2017

March 9, 2017

Hi I have the impression that if you - perform an implementor of a method (not closing the window) - then perform an rename method => you get a DNU ast Could I get some confirmation? Stef

1 0

ExternalForm was removed 10 days ago in 60413
by Aliaksei Syrel March 9, 2017

March 9, 2017

... and was moved to OSWindow-SDL2 as OSSDL2ExternalForm. If we require external form but don't want to depend on OSWindow what is the right way to go? Do we need to copy OSSDL2ExternalForm with project specific name? Advice with best practice would be nice :) Cheers, Alex

4 6

Segmentation fault on Moose 6.1 Build
by Blondeau Vincent March 9, 2017

March 9, 2017

Hi, The latest builds of the Moose6.1 image are failing due to a segmentation fault. Here is the link to the last build: https://ci.inria.fr/moose/job/moose-6.1/550/console How can we fix this? Thanks in advance, Cheers, Vincent !!!************************************************************************************* "Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

6 23

Archive Page for Pharo TechTalks
by Marcus Denker March 9, 2017

March 9, 2017

Hi, I added http://pharo.org/TechTalk <http://pharo.org/TechTalk> This is linked from http://pharo.org/community <http://pharo.org/community> The idea is to keep a log of all past tech talks with links to the archival recording (if there is one). Marcus

4 6

Callback regression in Pharo 6 (60437)
by Aliaksei Syrel March 9, 2017

March 9, 2017

Callback instantiation: createCallback > ^ FFICallback > signature: #(long (long)) > block: [ :value | value ] C functions: long test(long(*function)(long), long value) { > return function(value); } #include <limits.h> > > long long_min() { > return LONG_MIN; > } FFI calls: primCall: aCallback long: aNumber > ^ self ffiCall: #(long test(FFICallback aCallback, long aNumber)) > primLongMin > ^ self ffiCall: #(long long_min()) Test case: test > self > assert: (self primCall: self createCallback long: self primLongMin) equals: self primLongMin self primLongMin returns -2147483648 (= LONG_MIN). Result of callback is 0 => test fails. P.S. works in Pharo 5 Cheers, Alex

1 0

Need to login to access pharo-dev ci
by Yuriy Tymchuk March 9, 2017

March 9, 2017

HI, when I go to https://ci.inria.fr/pharo-contribution/ <https://ci.inria.fr/pharo-contribution/> I end up on a page asking me to login. Shouldnât it be possible to see the jobs without logging in? Uko

4 6

Esteban's ChangeLog week of 27 February 2017
by estebanlm＠gmail.com March 9, 2017

March 9, 2017

Hello! This is my weekly ChangeLog, from 27 February 2017 to 5 March 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=27/2/2017&to=5/3/2017 ChangeLog ========= 3 March 2017: ------------- * And now I made +libssh2.so+ compile on linux too :) I think Iceberg is fixed now for linux, can someone with linux try +vmLatest60+. * I worked on VM for linux, this time fixing dependencies for libgit2: it was not working because it was trying to link libssh2 existing in the system instead the one we provide (a problem with rpath)... I figured out I need to add some CMAKE options: ---- -DCMAKE_SKIP_BUILD_RPATH=FALSE -DCMAKE_INSTALL_RPATH="." ---- otherwise +make install+ was ignoring the +-Wl,rpath,.+ configuration. With this it seems to be working, but now I have a problem with +libssh2+ compilation. I'll see this next. * I took some moments to fix a problem on new UFFI version (0.26): Now, structures use a class variable to keep the offset value of a field. So now, instead having an accessor to a field of the form (for example): ---- MyStructure>>myField ^ handle unsignedLongAt: 42 ---- ... now you have an accessor of the form: ---- MyStructure>>myField ^ handle unsignedLongAt: OFFSET_MYFIELD ---- this is necesary to allow different platforms to use same structures (because sizes of fields, and in consequence of offsets of them inside a stricture are different). This 'offsets' are calculated (as structure compiled specs) at first access to +#compiledSpec+ of structure, which usually happens when you use it first time... but now always, as [case: 19788](https://pharo.fogbugz.com/f/cases/19788) shows. Well, now I fixed that :) 2 March 2017: ------------- * I added a Discord link on [http://pharo.org/community](http://pharo.org/community)... I want to slowly start moving our community there. I know Slack is very popular among us this days but Dicords offers some advantages (like no 10k limit on messages and a powerful search). 1 March 2017: ------------- * ... and now I made the [case:19783](https://pharo.fogbugz.com/f/cases/19783), to make SDL2 work on 64bits (it works!) :) * Yesterday I spent the full day debugging a VM to see why Athens was not working for 64bits and I finally figured out the problem was in image and not in VM :P As a result of the work, I produced this fixes: * [case:19781](https://pharo.fogbugz.com/f/cases/19781) to fix a problem answering pointers on callbacks. * [case:19782](https://pharo.fogbugz.com/f/cases/19782) to actually prepare Athens. With this two cases, Athens works in 64bits (almost) :) Now there is a problem in 64bits callbacks that makes the +VGTigerDemo runDemo+ to fail after some cycles. Since this problem does not happens on 32bits, I assume there is a problem on how callbacks work on 64bits. I'm not working on that (I will work also in migrating SDL2). 27 February 2017: ----------------- * Well, I spend some time trying to blindly figure out why athens may crash time to time when drawing surfaces, basically testing the apprachs [Ronie proposes](http://forum.world.st/Too-frequent-crashes-td4927143i20.html#a4934027). First approach consists on copying data to not rely on a surface at all. Problem with this is that it involves a whole full copy, that causes a lot of GC that pauses a lot the image... so smoothness is gone. Second approach seems a lot more doable, but I still don't know if it works: ---- Form subclass: #AthensCairoSurfaceForm instanceVariableNames: 'surface' classVariableNames: '' package: 'Athens-Cairo' AthensCairoSurfaceForm>>surface ^ surface AthensCairoSurfaceForm>>surface: anObject surface := anObject AthensCairoSurface>>asForm "create a form and copy an image data there" self checkSession. self flush. ^ (AthensCairoSurfaceForm extent: (self width@self height) depth: 32 bits: id) surface: self; yourself ---- this will prevent surfaces to be garbage collected before it's time and seems to be working fine (at least in my machine). cheers! Esteban

4 3

An implementation of a cache in instance variables
by Guillaume Larcheveque March 9, 2017

March 9, 2017

Hi, at Synectique, we are using cache for lots of projects and for now we were always using another instance variable or a dictionary to store many. It is complicated to maintain and we are always reinventing the wheel. That's why i created a first implementation (very naive but functional, documented and tested) of a cache. It is available here (with usage explication): http://smalltalkhub.com/#!/~GuillaumeLarcheveque/SmallCache and you can get it by doing: Metacello new smalltalkhubUser: 'GuillaumeLarcheveque' project: 'SmallCache'; configuration: 'SmallCache'; version: #development; load Tell me if you are interested in it or if you have ideas about it. -- *Guillaume Larcheveque*

1 0

Using PharoShortcuts for code completion
by komarlu2＠fit.cvut.cz March 9, 2017

March 9, 2017

Hello to all, would it be ok to implement a category in PharoShortcuts called "keymaps-code completion" where all the shortcuts for the suggestion menu and code completion would be? I think this menu would qualify as a basic tool. - In the comment section it says it is for basic tools and to allow to change shortcuts from a single place. Thanks, Lukas

2 1