- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] UnixOSProcessPlugin and accessing C array out of bounds

by stepharong

Thanks david! On Thu, 23 Feb 2017 03:00:08 +0100, David T. Lewis <lewis(a)mail.msen.com> wrote: > Holger, > > Good catch, thank you. There were two arrays dimensioned wrong in > OSProcessPlugin in > the Smalltalk slang source. I fixed this, and the warning should be gone > after the > sources are next generated. > > Esteban, > > I fixed the oscog branch also. I could not easily test it, but it is a > small change > so hopefully should be no problem when you next generate the plugin. > > Dave > > > On Wed, Feb 22, 2017 at 04:25:05PM +0700, Holger Freyther wrote: >> Hi Esteban, >> >> while building packages for OBS and going the compile warnings (one of >> the nice things of newer compilers is the increased diagnostic) I >> noticed this: >> >> [ 196s] >> /usr/src/packages/BUILD/src/plugins/UnixOSProcessPlugin/UnixOSProcessPlugin.c:4525:20: >> warning: iteration 64u invokes undefined behavior >> [-Waggressive-loop-optimizations] >> [ 196s] if ((semaIndices[sigNum]) > 0) { >> [ 196s] ^ >> [ 196s] >> /usr/src/packages/BUILD/src/plugins/UnixOSProcessPlugin/UnixOSProcessPlugin.c:4524:9: >> note: containing loop >> [ 196s] while (sigNum <= (signalArraySize())) { >> >> while (sigNum <= (signalArraySize())) { >> if ((semaIndices[sigNum]) > 0) { >> setSignalNumberhandler(sigNum, >> (originalSignalHandlers())[sigNum]); >> } >> sigNum += 1; >> } >> >> semaIndices has signalArraySize()/NSIG number of entries and is zero >> based, it is being accessed with sigNum==NSIG which means one entry >> beyond the memory of the array? Can you confirm this? >> >> restoreDefaultSignalHandlers >> "Restore signal handlers to their original behaviors." >> >> | sigNum | >> <returnTypeC: 'void'> >> semaIndices = nil "nil if in interpreter simulation" >> ifFalse: [sigNum := 1. >> [sigNum <= self signalArraySize] whileTrue: >> [((semaIndices at: sigNum) > 0) ifTrue: >> [self setSignalNumber: sigNum >> handler: (self originalSignalHandlers at: sigNum).]. >> sigNum := sigNum + 1]] >> >> So it is one based but the array doesn't have an extra element to make >> it work? How is this normally handled in slang code? >> >> >> holger > -- Using Opera's mail client: http://www.opera.com/mail/

Feb. 23, 2017

Re: [Pharo-dev] Build Pharo VM

by stepharong

Esteban can you add a todo to remove this readme? Stef On Thu, 23 Feb 2017 15:51:07 +0100, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> On 23 Feb 2017, at 15:33, Guido Chari <charig(a)gmail.com> wrote: >> >> Hi, >> >> I am trying to compile the Pharo-VM but I was not able. Neither in OSX >> nor in Unix. I followed the instructions on >> https://github.com/pharo-project/pharo-vm. In OSX the builder at >>the >> image level runs ok but I see no output at the build directory. In >> Unix, the files in the build directory were generated but then the >> building process fails because of some cmake >>files not found from one >> of the plugins. I am using the last version from the master repo. >> So my question is, any hints on what I am doing wrong? Are there any up >> to date documentation for building the vm? > > yes: everything :) > that instructions are very old and I still do not have time to fix themâ¦ > basically, if all your dependencies are ok, doing this should be enough: > $ git clone git@github.com:pharo-project/pharo-vm.git > $ cd pharo-vm/opensmalltalk-vm/build.macos32x86/pharo.cog.spur > $ ./mvm -f > > for linux you can: > $ cd pharo-vm/opensmalltalk-vm//build.linux32x86/pharo.cog.spur/build > $ ./mvm > > Esteban > >> >> Best regards, >> Guido. > -- Using Opera's mail client: http://www.opera.com/mail/

Feb. 23, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60410 Home: https://github.com/pharo-project/pharo-core

Feb. 23, 2017

[pharo-project/pharo-core] e65cbe: 60410

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: e65cbe9d4fdb5c5e7d5d9557e1232a5e625c5de2 https://github.com/pharo-project/pharo-core/commit/e65cbe9d4fdb5c5e7d5d9557… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-23 (Thu, 23 Feb 2017) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60409.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60410.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60409.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60410.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M UnifiedFFI-Tests.package/FFICallbackTests.class/instance/tests/testCqsort.st M UnifiedFFI-Tests.package/FFICallbackTests.class/instance/tests/testCqsortWithByteArray.st Log Message: ----------- 60410 19749 FFICallbackTests needs to be skipped for now https://pharo.fogbugz.com/f/cases/19749 http://files.pharo.org/image/60/60410.zip

Feb. 23, 2017

[pharo-project/pharo-core] f6558d: 60409

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f6558da26d4c7f3f14392533dc65b60a5c71f6ae https://github.com/pharo-project/pharo-core/commit/f6558da26d4c7f3f14392533… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-23 (Thu, 23 Feb 2017) Changed paths: R Kernel-Tests.package/ContextTest.class/instance/private/expectedFailures.st M ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-write barrier/testMakingObjectReadOnly.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60408.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60409.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60408.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60409.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R WriteBarrierTests.package/WriteBarrierTest.class/instance/setup/expectedFailures.st Log Message: ----------- 60409 19748 new VMs allow enabling of WriteBarrierTests https://pharo.fogbugz.com/f/cases/19748 http://files.pharo.org/image/60/60409.zip

Feb. 23, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60409 Home: https://github.com/pharo-project/pharo-core

Feb. 23, 2017

Re: [Pharo-dev] Build Pharo VM

by Esteban Lorenzano

> On 23 Feb 2017, at 15:33, Guido Chari <charig(a)gmail.com> wrote: > > Hi, > > I am trying to compile the Pharo-VM but I was not able. Neither in OSX nor in Unix. I followed the instructions on https://github.com/pharo-project/pharo-vm <https://github.com/pharo-project/pharo-vm>. In OSX the builder at the image level runs ok but I see no output at the build directory. In Unix, the files in the build directory were generated but then the building process fails because of some cmake files not found from one of the plugins. I am using the last version from the master repo. > > So my question is, any hints on what I am doing wrong? Are there any up to date documentation for building the vm? yes: everything :) that instructions are very old and I still do not have time to fix themâ¦ basically, if all your dependencies are ok, doing this should be enough: $ git clone git@github.com:pharo-project/pharo-vm.git $ cd pharo-vm/opensmalltalk-vm/build.macos32x86/pharo.cog.spur $ ./mvm -f for linux you can: $ cd pharo-vm/opensmalltalk-vm//build.linux32x86/pharo.cog.spur/build $ ./mvm Esteban > > Best regards, > Guido.

Feb. 23, 2017

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

by Ben Coman

Not great but okay. i think we are at the point of "perfect is the enemy of done". There have been plenty of suitable suggestions, and its a topic with high bike-shedding quotient, so you should just pick one you and the man paying the bills are happy with. Otherwise you'll get another round of suggestions like these... "phrem" 26k googs - pharo remote "phremt" - 195 googs - pharo remote tools "phremit" 225 googs - pharo remote integrated tools "phremide" 5 googs - pharo remote ide One thing to keep in mind though is that we can be as clever as we like here in text, but you should imagine yourself saying it in front of a lecture. cheers -ben On Thu, Feb 23, 2017 at 5:35 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Philippe invented new word Pharocket :). Maybe it is the best for this > project? > > > 2017-01-30 17:09 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > >> Also I think its fair that the guy that wrote the code to pick the name, >> its his baby afterall, whether he is paid for it or not. He earned that >> right. >> >> On Mon, Jan 30, 2017 at 6:06 PM Dimitris Chloupis <kilon.alios(a)gmail.com> >> wrote: >> >>> Just for the record, the name does not matter >>> >>> As a matter of fact if you want the name to really sell the library/ >>> tools then the last thing you want is a name that makes any logical sense >>> >>> You have much better chance to catch attention with "Pink Elephant" than >>> "Pharo Remote tools" or whatever >>> >>> illogical names monopolise the software market >>> >>> Python >>> Ruby on Rails >>> Django >>> Blender >>> Unreal >>> Unity >>> Javascript >>> Java >>> C >>> C++ >>> Windows >>> MacOS >>> >>> and so on >>> >>> Developers choose to name their projects the craziest names and wisely so >>> >>> the name is there to catch attention, not to make sense or come up top >>> on google search. >>> >>> In the end what it matters is the code itself. >>> >>> Ruby On Rails did not become populary because we love ruby stones or we >>> love go "too...tooooooo" on rails ... its popular because the library has >>> been very useful to many people. >>> >>> And the name itself guarantees that it wont come up top in google search >>> because it has nothing unique about it. >>> >>> The rest is just marketing ;) >>> >> >

Feb. 23, 2017

Build Pharo VM

by Guido Chari

Hi, I am trying to compile the Pharo-VM but I was not able. Neither in OSX nor in Unix. I followed the instructions on https://github.com/pharo-project/pharo-vm. In OSX the builder at the image level runs ok but I see no output at the build directory. In Unix, the files in the build directory were generated but then the building process fails because of some cmake files not found from one of the plugins. I am using the last version from the master repo. So my question is, any hints on what I am doing wrong? Are there any up to date documentation for building the vm? Best regards, Guido.

Feb. 23, 2017

Re: [Pharo-dev] Pharo Papers

by denker

Hello, I have setup a collection at HAL. For now it is empty, we should fill it and then add it to the website (and announce it then, not nowâ¦). The collection automatically has every paper on HAL that has âPHAROâ as a keyword in the field "Project/Collaborationâ. https://hal.inria.fr/PHARO/ https://hal.archives-ouvertes.fr/PHARO HAL is not Inria specific, here is some more infos (from https://hal.archives-ouvertes.fr ): HAL is an open archive where authors can deposit scholarly documents from all academic fields. For the attention of the authors â¢ The deposit must be made in agreement with the co-authors and in the respect for the policy of the publishers. â¢ The deposit is subject of a control, HAL reserves the right to refuse items that do not meet the criteria of the archive. â¢ Any deposit is definitive, no withdrawals will be made after the on-line posting of the publication. â¢ Text files in pdf format or image files are sent to CINES (https://www.cines.fr/en/) for long-term archiving. For the attention of the readers â¢ In a context of electronic distribution, every author keep all its intellectual property rights. > On 16 Feb 2017, at 15:13, denker <marcus.denker(a)inria.fr> wrote: > > One idea on my TODO that I got from colleagues here working on another OpenSource/Research > system (Sofa3D): to add all publication to the website automatically using HAL (the national french > paper database). > > It looks like this on the website: > https://www.sofa-framework.org/applications/publications/ > > and here âhow to add a paperâ: > > https://www.sofa-framework.org/applications/publications/add-a-publication-… > > I will definitely set this up for Pharo later this year (read: as soon as possible) > > Marcus > > >> On 16 Feb 2017, at 14:30, Ben Coman <btc(a)openinworld.com> wrote: >> >> And now for your regularly scheduled random trivia show... >> I was mildly curious about how many papers touched on Pharo. >> >> 1,110 on google scholar for... >> "pharo" "programming" >> http://tiny.cc/pharo-scholar >> >> 1,630 on normal google for... >> "pharo" "programming" "abstract" "introduction" "conclusion" >> "references" filetype:pdf >> http://tiny.cc/pharo-papers >> >> Probably a lot of overlap between them. >> cheers -ben >> >

Feb. 23, 2017