November 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] NAtiveBoost error

by Igor Stasenko

NBExternalArray instances cannot be passed directly to functions expecting pointers. use 'myarray address' for arguments. On 3 November 2014 00:20, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: > Hi, > > I have a problem with a nativeboost call, but I don't see what I do wrong. > > library function prototype is: > int zmq_getsockopt (void *socket, int option_name, void *option_value, > size_t *option_len); > > my calling method in pharo is: > zmq_getsockopt: socket option_name: option_name option_value: option_value > option_len: option_len > <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: > errorCode> > ^self nbCall: #(int zmq_getsockopt (void *socket, int option_name, > void * option_value, size_t* option_len) ) > > when I call it with > ... > optionValue := (NBExternalArray ofType: 'int') externalNew: 1. > optionLen := (NBExternalArray ofType: 'size_t' ) externalNew: 1. > [ optionValue at: 1 put: 0 . > optionLen at: 1 put: (NBExternalType sizeOf: 'int') . > rc := self zmq_getsockopt: socket option_name: option_name > option_value: optionValue > option_len: optionLen . > value := optionValue at: 1 . > ] ensure: [ optionValue free. > optionLen free ]. > ... > I allways get an exception: "error during FFI call : nil" > > > After stepping in NBFFICallout generation, I found something strange, the > code > generation seems not to be called because lastError stays at nil ? > > handleFailureIn: aContext nativeCode: aBlock > lastError := self getErrorFrom: aContext lastError: NativeBoost > lastError. > > >>getErrorFrom: aContext lastError: errorCode > ... checks pragmas etc > >>getErrorFrom: aContext lastError: errorCode > ... lastError := aContext tempAt: method numTemps. > => lastError = nil ??? shouldn't be > ErrNoNativeCodeInMethod ? > "install native code and retry the send" > lastError = ErrNoNativeCodeInMethod > ifTrue: [ ^ self generateCode: aBlock andRetry: aContext ]. > never gets called ... > > "ok, we're out of options, signal an error here" > ^ self signalError: lastError > > Could it be because I use this image on windows and unix ? > Or because I had an exception at prototype parsing the first time > because I forgot a ; at the end of the prototype ? > > Is my prototype correct or is it the origin of the error ? > Is there a way to reset the lastError (aContext tempAt: method numTemps) ? > I will try to reset it in debugger but may be there is a cleaner way ? > would it be ok to change the test in handleFailure to > (lastError = ErrNoNativeCodeInMethod) or:[ lastError isNil ] ? > (I can open a bug in this case ) > > Any idea or comment is welcome > Thanks in advance > > Alain > > > -- Best regards, Igor Stasenko.

Nov. 3, 2014

NAtiveBoost error

by Alain Rastoul

Hi, I have a problem with a nativeboost call, but I don't see what I do wrong. library function prototype is: int zmq_getsockopt (void *socket, int option_name, void *option_value, size_t *option_len); my calling method in pharo is: zmq_getsockopt: socket option_name: option_name option_value: option_value option_len: option_len <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: errorCode> ^self nbCall: #(int zmq_getsockopt (void *socket, int option_name, void * option_value, size_t* option_len) ) when I call it with ... optionValue := (NBExternalArray ofType: 'int') externalNew: 1. optionLen := (NBExternalArray ofType: 'size_t' ) externalNew: 1. [ optionValue at: 1 put: 0 . optionLen at: 1 put: (NBExternalType sizeOf: 'int') . rc := self zmq_getsockopt: socket option_name: option_name option_value: optionValue option_len: optionLen . value := optionValue at: 1 . ] ensure: [ optionValue free. optionLen free ]. ... I allways get an exception: "error during FFI call : nil" After stepping in NBFFICallout generation, I found something strange, the code generation seems not to be called because lastError stays at nil ? handleFailureIn: aContext nativeCode: aBlock lastError := self getErrorFrom: aContext lastError: NativeBoost lastError. >>getErrorFrom: aContext lastError: errorCode ... checks pragmas etc >>getErrorFrom: aContext lastError: errorCode ... lastError := aContext tempAt: method numTemps. => lastError = nil ??? shouldn't be ErrNoNativeCodeInMethod ? "install native code and retry the send" lastError = ErrNoNativeCodeInMethod ifTrue: [ ^ self generateCode: aBlock andRetry: aContext ]. never gets called ... "ok, we're out of options, signal an error here" ^ self signalError: lastError Could it be because I use this image on windows and unix ? Or because I had an exception at prototype parsing the first time because I forgot a ; at the end of the prototype ? Is my prototype correct or is it the origin of the error ? Is there a way to reset the lastError (aContext tempAt: method numTemps) ? I will try to reset it in debugger but may be there is a cleaner way ? would it be ok to change the test in handleFailure to (lastError = ErrNoNativeCodeInMethod) or:[ lastError isNil ] ? (I can open a bug in this case ) Any idea or comment is welcome Thanks in advance Alain

Nov. 2, 2014

Re: [Pharo-dev] Experience makers

by Yuriy Tymchuk

> On 01 Nov 2014, at 22:15, stepharo <stepharo(a)free.fr> wrote: > > > On 27/10/14 13:44, Yuriy Tymchuk wrote: >> To summarise Iâd like to propose adding startup scripts manager to pharo luncher. > I'm not sure that there are startup scripts. But yes you got what I meant. a super simple way to load a bunch of projects in another image based on the current one. The projects that I know are using startup actions [1][2]. These are files that go into ~/Library/Preferences/pharo/ and define what has to be run on image startup. They are used to âcustomizeâ your image. Uko [1]: https://github.com/RobertoMinelli/DFlow/blob/master/installDFlow.st <https://github.com/RobertoMinelli/DFlow/blob/master/installDFlow.st> [2]: http://smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter <http://smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter> >> Whatâs more, usually we are working on our one âprojectâ. And as itâs a good practice to start from a fresh image, we either have to load a configuration of it into fresh images or download pre-built image from CI. And we are too bound to CI because of image building. What I see as next step in the development workflow, is to say to the launcher: I want this Project is this Image (3.0, 4.0) with this prefs (experiences). The launcher builds the thing and you can work with it. >> >> In general I like your idea a lot, but letâs have a little discussion to hear what the others have to say. > > :) > > and I would like a button that say: snapshot this image as my project :) > (the system should have a way to know the system package versus others. it should be possible with some metadata :) > > I know that I'm lazy (and bored to redo all the time the same thing :)) > >> >> Uko >> >>> On 27 Oct 2014, at 13:13, stepharo <stepharo(a)free.fr> wrote: >>> >>> Dear experience makers (Martin, yuriy, tommaso, roberto and others,) >>> >>> you would like to have many people doing your experience.... I know you would love that. >>> Here is my suggestion: ease the use of new images. >>> Each time I want to load the projects I'm hacking and I do not have a jenkins for it, it is painful (setting up >>> the repos.... loading....). So I do not change often images and I'm reluctant to load new stuff (like your experiments) >>> >>> >>> - build a simple little tool that could be integrated in pharo and would do the following: >>> - let the user (un)/select some packages or configurations >>> - generate a script to reload these configurations really easily >>> >>> This way I can load my project and then you provide a script for your experience. >>> and after I can reload my project with your material for experience in my new image. >>> Right now I do not like to hack the preference file because I have images where I do not want any interference >>> >>> So is my proposal clear? >>> >>> Stef >>> >> >> > >

Nov. 2, 2014

Re: [Pharo-dev] [Vm-dev] Re: Super fast delay

by Eliot Miranda

Hi Ben, On Nov 2, 2014, at 6:06 AM, Ben Coman <btc(a)openInWorld.com> wrote: > Eliot Miranda wrote: >> On Wed, Oct 29, 2014 at 12:14 PM, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: >> Holger Hans Peter Freyther wrote: >> On Wed, Oct 29, 2014 at 06:54:57PM +0100, Holger Hans Peter >> Freyther wrote: >> On Wed, Oct 29, 2014 at 10:03:03AM +0100, Norbert Hartl wrote: >> Good Evening, >> Hi again, >> I don't know how you debug startUp issues. I just added an >> OrderedCollection >> into the systemdictionary and use it as a log.. >> time ./bin/pharo --nodisplay ./TimerTest3.image eval "(Delay >> forSeconds: 3) wait. (Smalltalk at: #Foo) do: [:each | >> FileStream stderr nextPutAll: each printString; cr].1" >> ... old events from saving the image... >> {#handleTimerEvent->7147} >> {#handleTimerEvent->7167} >> {#resumptionTime->7187} >> {#handleTimerEvent->7167} >> {#handleTimerEvent->7187} >> {#start->true} >> {#start->393102159} >> {#start->393102159} >> {#resumptionTime->3279} >> {#handleTimerEvent->279} >> {#adjustResum->-393098880} >> {#restoreWithActiveDelay->266} >> {#adjustResum->-393098601} >> 1 >> real 0m0.294s >> user 0m0.244s >> sys 0m0.048s >> So what happens is Delay class>>#startU is called. and >> ActiveDelayStartTime is being set to 393102159. Then the >> delay is being created and resumptionTime is set to 3279. >> At the first time handleTimerEvent runs the milliSecondClock >> jumped backwards from 393102159 to 3279 which leads to >> an adjustment of the time. >> a.) Why does the time jump backwards like this during the >> resumption of the image? "3279" is not the old time nor >> the new starting time. >> b.) So even if that is a "wrap" around. Why does it go >> wrong? Are there unit tests for the clock wraps around? >> There are no unit tests, I guess since its all done using class >> variables its too hard test without disturbing the system. >> Now I have spent the last week refactoring this out to the >> instance-side of a new class "DelayScheduler" which should help with >> getting unit tests. Its ready for review [1], maybe you could take >> a look. >> [1] https://pharo.fogbugz.com/__default.asp?14261 >> <https://pharo.fogbugz.com/default.asp?14261> >> Maybe it is the same reason delays just don't work after >> image resumption? >> The "first" issue appears that when start is being executed >> that the clock is still wrong. At the same the clock is >> being considered wrapped the resumption time was actually >> already "correct' (3279 instead of 393102159+3279). >> Does this ring a bell? >> holger >> btw, its too late in the night for me to try something, but I have >> been wondering, should the check for clock roll-over occur >> immediately after >> TimingSemaphore wait >> wakes up. That is, before the Schedule and Finish requests are >> handled ??? >> The check for rollover should be thrown away and the system implemented over the VM's support for 64-bit microseconds since 1901. It's in the VM, it isn't susceptible to rollover for ~ 50,000 years, and doesn't require the millisecond clock to be synced to the second clock, because all times can be derived from the one 64-bit microsecond clock. >> -- >> best, >> Eliot > > The performance of the Delay timer event loop is noted in the code to be critical, however... > > "Time millisecondClockValue" returns a SmallInteger, which is an immediate object while "Time microsecondClockValue" returns a LargePositiveInteger, which is not. > > So theoretically will calculations and comparisons based on the second be slower ? Actually my performance testing so far hasn't found it to be slower, but I am interested in the general case. That comment was written when the context interpreter VM was the standard. Cog is much faster. That should more than make up for the small amount of large integer arithmetic the use of 64-bit microseconds involves. And once we switch to 64-bit Spur the 64-bit microsecond clock will once again be a SmalInteger. And if your measurements show you there isn't an issue then there isn't an issue. > > cheers -ben

Nov. 2, 2014

Re: [Pharo-dev] Make Nautilus to automatically categorize new methods (if needed) and remove empty protocols

by stepharo

Thanks > Hi, > > cf. https://pharo.fogbugz.com/default.asp?14376 > to eventually integrate. > > Cheers, > > #Luc

Nov. 2, 2014

Re: [Pharo-dev] encodings and regex clash?

by Sven Van Caekenberghe

StÃ©ph, For me all this works and gives the same result: '<head> -BASE- <title>Dr. Stéphane Ducasse</title> </head>' copyWithRegex: '-BASE-' matchesReplacedWith: '<p>Foo</p>'. 'foo.html' asFileReference writeStreamDo: [ :out | out << '<head> -BASE- <title>Dr. Stéphane Ducasse</title> </head>' ]. 'foo.html' asFileReference contents copyWithRegex: '-BASE-' matchesReplacedWith: '<p>Foo</p>'. Sven > On 02 Nov 2014, at 16:15, Max Leske <maxleske(a)gmail.com> wrote: > > >> On 02.11.2014, at 14:59, stepharo <stepharo(a)free.fr> wrote: >> >> >> On 2/11/14 12:37, Max Leske wrote: >>>> On 01.11.2014, at 22:07, stepharo <stepharo(a)free.fr> wrote: >>>> >>>> Hi guys >>>> >>>> I'm doing a small variable expansion to relocate my webpage. I want to expand -base- into <base>http://sdmeta.gforge.inria.fr</base> >>>> Now it works when I test with some strings inside the image >>>> >>>> >>>> trying >>>> "self new trying" >>>> >>>> ^ self sample >>>> copyWithRegex: '-BASE-' >>>> matchesReplacedWith: self baseString. >>>> >>>> sample >>>> >>>> >>>> ^ '<?xml version="1.0" encoding="ISO-8859-1"?> >>>> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> >>>> <link rel="stylesheet" href="stef.css"/> >>>> <head> >>>> -BASE- >>>> <title>Dr. Stéphane Ducasse</title> >>>> </head>' >>>> >>>> baseString >>>> ^ '<base>http://sdmeta.gforge.inria.fr </base>' >>>> >>>> self new trying results >>>> >>>> '<?xml version="1.0" encoding="ISO-8859-1"?> >>>> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> >>>> <link rel="stylesheet" href="stef.css"/> >>>> <head> >>>> <base>http://sdmeta.gforge.inria.fr </base> >>>> <title>Dr. Stéphane Ducasse</title> >>>> </head>' >>>> >>>> and this is good. >>>> >>>> Now when I work with a stream it does. >>>> >>>> >>>> >>>> contentsOf: aFileSystemFile >>>> "self new contentsOf: (FileSystem workingDirectory / 'Books.html') " >>>> contents := aFileSystemFile readStream contents >>>> >>>> tryingContents >>>> "self new tryings" >>>> >>>> ^ self sample >>>> copyWithRegex: '-BASE-' >>>> matchesReplacedWith: contents. >>> >>> Whatâs the âwrongâ output you get here? >> >> In fact I get the stream contents but the regex does not match. >> I suspect a problem with the encodings of the file. Do you have an idea? Stef > > Noâ¦ I donât see how encoding could be a problem. Can you create a minimal working (failing) test file and post it? >

Nov. 2, 2014

Re: [Pharo-dev] Failing #obsoleteClasses test

by Max Leske

> On 02.11.2014, at 18:28, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Max, > > could the cache be reimplemented using WeakArray? Stuff like this is a drag. eg in Squeak the Windows menu holds onto all the windows that were open when last the menu was opened. So to get a window reclaimed after being closed if you opened the Windows menu you have to open it again. I must fix that. No idea. I really didnât look at what it does, I just tracked pointers ;) But yes, maybe that would be a good idea. Adding âASTCache reset.â all over the place is not really a good strategy. Iâll send a copy of this message to Marcus and ClÃ©ment; I suspect they might know more about the AST stuff. Cheers, Max > > Eliot (phone) > > On Nov 2, 2014, at 8:43 AM, Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>> wrote: > >> I spent a couple of hours trying to find out why the #obsoleteClasses test sporadically fails. Iâve found one candidate that fixes all the failures that I could produces. Simply put, any test that does something AST related (e.g. runs critics) *has to* reset the ASTCache during #tearDown: >> >> ASTCache reset. >> >> Iâve found two test classes that needed to be adapted: SmalllintManifestCheckerTest and VSReleaseDevelopmentVersionCommandTest. >> >> Issue with slice: https://pharo.fogbugz.com/f/cases/14375/Random-obsoleteClasses-test-failures <https://pharo.fogbugz.com/f/cases/14375/Random-obsoleteClasses-test-failures> >> >> Cheers, >> Max

Nov. 2, 2014

ImageCleaner interaction with Delay

by Ben Coman

ImageCleaner>>cleanUpForRelease calls >>cleanUpMethods which calls Delay class>>startTimerEventLoop. I thought this would have started with a clean/empty suspended delays heap, but it carries forward the old SuspendedDelays. So if there happened to be a suspended delay expiring in a month's time, that would not be affected by ImageCleaner and would end up in the release. I believe the correct behaviour would be for ImageCleaner to produce a clean/empty suspended delays, and so that no waiting processing get stuck, signal any remaining suspended delays when the timer event loop is stopped by Delay class>>stopTimerEventLoop. Any objections? cheers -ben

Nov. 2, 2014

Re: [Pharo-dev] Failing #obsoleteClasses test

by Ben Coman

Max Leske wrote: > I spent a couple of hours trying to find out why the #obsoleteClasses > test sporadically fails. Iâve found one candidate that fixes all the > failures that I could produces. Simply put, any test that does something > AST related (e.g. runs critics) *has to* reset the ASTCache during > #tearDown: > > ASTCache reset. > > Iâve found two test classes that needed to be > adapted: SmalllintManifestCheckerTest > and VSReleaseDevelopmentVersionCommandTest. > > Issue with > slice: https://pharo.fogbugz.com/f/cases/14375/Random-obsoleteClasses-test-failures > > Cheers, > Max nice find.

Nov. 2, 2014

Make Nautilus to automatically categorize new methods (if needed) and remove empty protocols

by Luc Fabresse

Hi, cf. https://pharo.fogbugz.com/default.asp?14376 to eventually integrate. Cheers, #Luc

Nov. 2, 2014