- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] cd0c2a: 40258

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: cd0c2a5b48863570bbdc74f4fc74f80ad07edf39 https://github.com/pharo-project/pharo-core/commit/cd0c2a5b48863570bbdc74f4… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-26 (Fri, 26 Sep 2014) Changed paths: A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script258.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40258.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Inspector.package/ContextTempEyeElement.class/instance/accessing/value.st M Tool-ImageCleaner.package/ImageCleaner.class/instance/api/cleanUpForRelease.st Log Message: ----------- 40258 14048 two tests failing in EmbeddedFreeTypeFontInstallerTest https://pharo.fogbugz.com/f/cases/14048 14079 Inconsistent information in debugger (pharo 4) https://pharo.fogbugz.com/f/cases/14079 http://files.pharo.org/image/40/40258.zip

Sept. 26, 2014

[pharo-project/pharo-core]

by GitHub

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

Sept. 26, 2014

[pharo-project/pharo-core]

by GitHub

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

Sept. 26, 2014

[pharo-project/pharo-core] 3d10c1: 40257

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 3d10c184f231f8191bdd9c6e25f9170138abb58c https://github.com/pharo-project/pharo-core/commit/3d10c184f231f8191bdd9c6e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-26 (Fri, 26 Sep 2014) Changed paths: M FreeType.package/FreeTypeFontProvider.class/instance/file paths/guessWindowsFontFolderPath.st M KernelTests.package/BlockClosureTest.class/instance/tests/testTallyInstructions.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script257.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40257.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-MorphicAdapters.package/MorphicButtonAdapter.class/instance/factory/buildWidget.st Log Message: ----------- 40257 14061 windows systemfonts : wrong path in guessWindowsFontFolderPath https://pharo.fogbugz.com/f/cases/14061 13131 Spec weirdness > MNU ToolDockingBarMorph>>popupEvent:in: on right click on button https://pharo.fogbugz.com/f/cases/13131 14072 Failing test: BlockClosureTest>>#testTallyInstructions https://pharo.fogbugz.com/f/cases/14072 http://files.pharo.org/image/40/40257.zip

Sept. 26, 2014

[pharo-project/pharo-core] 6c960a: 40256

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 6c960a5d467c81f19d419a3aa0389b634bec60c9 https://github.com/pharo-project/pharo-core/commit/6c960a5d467c81f19d419a3a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-26 (Fri, 26 Sep 2014) Changed paths: R Kernel.package/PseudoClassOrganization.class/README.md R Kernel.package/PseudoClassOrganization.class/definition.st R Kernel.package/PseudoClassOrganization.class/instance/comment accessing/classComment.st R Kernel.package/PseudoClassOrganization.class/instance/comment accessing/classComment_.st R Ring-Core-Kernel.package/RGFactory.class/README.md R Ring-Core-Kernel.package/RGFactory.class/class/class initialization/current.st R Ring-Core-Kernel.package/RGFactory.class/definition.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory/createMethodNamed_parent_.st M Ring-Core-Kernel.package/extension/ChangeRecord/instance/createCommentDefinition.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testAddingMethods.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testRemovingMethods.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testWithProtocols.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testExistingMethodWithClass.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testExtensionMethod.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testMethodEquality.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testNonExistingMethodWithClass.st M Ring-Tests-Kernel.package/RGTraitDefinitionTest.class/instance/testing/testAddingMethods.st M SUnit-UI.package/TestRunner.class/instance/accessing-ui/buttons.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script256.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40256.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-FilePackage.package/PseudoClassOrganization.class/README.md A System-FilePackage.package/PseudoClassOrganization.class/definition.st A System-FilePackage.package/PseudoClassOrganization.class/instance/comment accessing/classComment.st A System-FilePackage.package/PseudoClassOrganization.class/instance/comment accessing/classComment_.st M Traits.package/TClass.class/instance/initialize-release/sharing_.st Log Message: ----------- 40256 14069 Finish cleaning RGFactory https://pharo.fogbugz.com/f/cases/14069 14077 Move PseudoClassOrganization close to PseudoClass https://pharo.fogbugz.com/f/cases/14077 13738 MNU: CompiledMethod>>hasRun https://pharo.fogbugz.com/f/cases/13738 13705 Shared pool incorrectly defined as global https://pharo.fogbugz.com/f/cases/13705 http://files.pharo.org/image/40/40256.zip

Sept. 26, 2014

[pharo-project/pharo-core]

by GitHub

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

Sept. 26, 2014

Re: [Pharo-dev] new VMs promoted ad stable

by Esteban Lorenzano

â¦ and I needed to revert :( there is an annoying bug when building the minimal versions, and we need it running for the sprint today, so I reverted and I will check the problem later. cheers, Esteban On 25 Sep 2014, at 22:45, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > yeahâ¦ so? :) > I just promoted a new stable version with *less bugs*, not *bug free* :P > seriously: I didnât have the time to check at the issue, Iâm sorryâ¦ (though it is in my TODO list...) > > Esteban, the orchestra-man > > <attachment.jpeg> > > > On 25 Sep 2014, at 22:38, Torsten Bergmann <astares(a)gmx.de> wrote: > >> Hi Esteban, >> >> But the Windows VM still has this bug, see here >> >> http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2014-September/1… >> >> and here >> >> https://pharo.fogbugz.com/f/cases/13995/Recent-Windows-VM-does-not-reopen-f… >> >> cheers, >> T. >> >>> Gesendet: Donnerstag, 25. September 2014 um 17:53 Uhr >>> Von: "Esteban Lorenzano" <estebanlm(a)gmail.com> >>> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >>> Betreff: [Pharo-dev] new VMs promoted ad stable >>> >>> Hi, >>> >>> I promoted latest VMs to stable. >>> Not many changes, but at least infamous SmallInteger bug should not be there anymore. >>> >>> cheers, >>> Esteban >>> >

Sept. 26, 2014

Re: [Pharo-dev] catching FFI errors

by Eliot Miranda

Hi Ben, On Sep 25, 2014, at 5:50 PM, Ben Coman <btc(a)openInWorld.com> wrote: > > I had a brief moment wondering about the general problem we have when calling out through FFI that we expose ourselves to bugs in the external library that crash the Image. I wonder... > > 1. Debuggers like gdb can run a program that crashes, without themselves itself crashing. Could our FFI calls be wrapped in similar mechanism? > > 2. Languages have exception handling, so that errors like divide by zero can be caught. Could our FFI calls be wrapped in similar mechanism? > cheers -ben one thing that is pretty straight-forward to do is to catch and report errors during FFI calls as primitive failures with error codes. I added this to the VisualWorks VM a while ago It works like this: 1. The VM installs a first-level exception handler (windows) or signal handlers for SIGSEGV et al (unix). (This is something the VM already does). 2. When an FFI call out is made the VM can find the activation they made an FDI call out. It must be able to do this if it is to handle a callback. 3. An FFI call out is modified to set a flag, eg inFFICall, that is tested by the first-level exception handler. The flag is cleared when the FFI call completes or cleared when taking a callback and restored when the callback returns. 4. When the first level exception/signal handler is invoked it tests the inFFICall flag. If unset it does what it always did (exit, do nothing, etc). If the flag is set it collects the error information, located the FFI activation for the FFI call, does a long jump that returns from the FFI call as a primitive failure, supplying the error information. Now this is useful because the VM doesn't crash (provided the error was localized in its effects and didnt eg corrupt the heap), and hence easy for the developer to find out which FFI call provoked the error, but not as useful as catching the error in gdb. The exception info is typically an exception code and an address, which may be difficult for the programmer to decode. Hence the mechanism needs to be made optional, typically in by default, and then disabled to investigate under gdb. Does this sound useful? Eliot (phone)

Sept. 26, 2014

Re: [Pharo-dev] [Pharo-users] Your picture on Pharo contributors :)

by Serge Stinckwich

If you have a gravatar picture, you can generate a 70x70 picture like that: (ZnEasy getJpeg: 'http://www.gravatar.com/avatar/', (ZnDigestAuthenticator md5Hash: 'serge.stinckwich(a)gmail.com'),'?s=70' ) asMorph openInWorld On Fri, Sep 26, 2014 at 7:55 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 26 Sep 2014, at 07:25, stepharo <stepharo(a)free.fr> wrote: > >> Hi guys >> >> do not forget to sign the license agreement >> http://files.pharo.org/media/PharoSoftwareDistributionAgreement.pdf >> and send us your picture to be added to >> http://pharo.org/about >> >> Stef > > The picture should be a 70x70 PNG. > > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Sept. 26, 2014

Re: [Pharo-dev] Building .deb with Pharo VM

by Jan Vrany

Hi Markus & Damien, Markus, thanks for the hint, I'll try. Damien, yes, the problematic patch was source-hardening.patch as Markus pointed out. And then also something about native vs. quilt package format. So far I struggled with recipe given by Clement, mainly because of libgit2 - it refuses to compile cleanly in 32bit mode under 64bit system (I had this problem 2 years ago when playing with libgit2, apparently no progress here :-) Bit of sed would do it, although super ugly. Then the vm generator generated sources to the wrong directory. It either does not respect process CWD os it was something else... However, I already exhausted my free time. I'll try again later and get back to you. Best, Jan On Thu, 2014-09-25 at 15:37 +0200, Markus Fritsche wrote: > On 2014-09-25 13:58, Damien Cassou wrote: > > >> I tried that,but some patches applied to the sources above are rejected > >> so package dpkg-buildpackage fails - at least on Debian Jessie > > > can you give more information? > > source-hardening.patch has to be adjusted > > --- a/src/vm/cogit.c 2014-09-24 11:26:13.117242533 +0200 > +++ b/src/vm/cogit.c 2014-09-24 11:26:55.181154041 +0200 > @@ -19339,7 +19339,7 @@ printTrampolineTable(void) > for (i = 0; i < trampolineTableIndex; i += 2) { > printHex(((sqInt)(trampolineAddresses[i + 1]))); > print(": "); > - print(((char *) (trampolineAddresses[i]))); > + printf("%s", trampolineAddresses[i]); > cr(); > } > } > > > Kind regards, > Markus >

Sept. 26, 2014