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

Re: [Pharo-dev] [squeak-dev] vm crash from BalloonEngine (maybe B2DPlugin or BitBltPlugin)

by Nicolai Hess

2015-04-08 20:02 GMT+02:00 karl ramberg <karlramberg(a)gmail.com>: > Confirmed. > > Karl > > On Wed, Apr 8, 2015 at 5:33 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> In order to reproduce it, draw a rectangle with radial gradient fill, >> with direction >> and normal, both of length 1. >> > This is not the reason why it crashes. It happens for other values as well: |form canvas fill direction normal| direction := 4@0. normal := 0@2. form := Form extent:300@300 depth:32. canvas := form getCanvas. fill := GradientFillStyle new colorRamp:{0 -> Color white . 0.5 -> Color green . 1 -> Color blue};origin:400@400 ;direction:direction;normal:normal;radial:true;yourself. canvas fillRectangle: (0@0 extent:800@800) fillStyle: fill. Display getCanvas drawImage: form at: 300@300 This uses a different value for direction and normal and the fill is defined for a larger area (800x800) -> CRASH Maybe, this is a rare bug, because, normally you don't create a small gradient t o fill a large area. But a vm crash is not nice, I would like to get this fixed. I am not sure what is the exact cause, but it may come from a signed integer overflwo, It looks like Balloon uses fixed point arithmetik (binary scaling). This fixed point representation (16.16 bit fixed point represented in a 32 integer) tend to overflow, especially for operations like computing the squared length of a vector x*x+y*y -> overflow -> result is a negative number. Possible solutions: downscale prior to the multiplication -> lost of precision use a larger datatype for intermediate results. It looks like B2D uses the first option (look at senders of accurateLengthOfwith and squaredLenghtOfwith Maybe there is something wrong with the other code that multiplies the values, or the 16.16 bit fixed point is just not large enough for some fills? Any ideas? Nicolai > >> This one works (no vm crash): >> |form canvas fill direction normal| >> direction := 1@0. >> normal := 0@0. >> form := Form extent:300@300 depth:32. >> canvas := form getCanvas. >> fill := GradientFillStyle new colorRamp:{0 -> Color white . 0.5 -> Color >> green . 1 -> Color blue};origin:150@150 >> ;direction:direction;normal:normal;radial:true;yourself. >> canvas fillRectangle: (50@50 extent:200@200) fillStyle: fill. >> Display getCanvas drawImage: form at: 300@300. >> >> >> direction := 1@0. >> normal := 0@0. >> -> OK >> >> direction := 0@0. >> normal := 0@1. >> -> OK >> >> direction := 1@0. >> normal := 0@1. >> -> VM-Crash (Pharo and Squeak) >> >> Pharo: >> VM Version: Cog VM 4.0.0 (release) from Feb 16 2015 >> Compiler: gcc 4.6.2 >> Interpreter Build: NBCoInterpreter >> NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: >> 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Feb 16 2015 >> Cogit Build: NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: >> 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Feb 16 2015 >> Source Version: https://github.com/pharo-project/pharo-vm.git Commit: >> 55fbd0b0279998a4a33852f5afb3d213986cc3ae Date: 2015-02-16 17:54:00 +0100 >> By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14895 >> >> Current byte code: -1 >> Primitive index: 117 >> Smalltalk stack dump: >> 0x24c830 M BalloonEngine>copyLoopFaster 0x6b09b80: a(n) BalloonEngine >> 0x24c848 M BalloonEngine>copyBits 0x6b09b80: a(n) BalloonEngine >> 0x24c860 M BalloonEngine>postFlushIfNeeded 0x6b09b80: a(n) BalloonEngine >> 0x24c884 I >> BalloonEngine>drawRectangle:fill:borderWidth:borderColor:transform: >> 0x6b09b80: a(n) BalloonEngine >> 0x24c8b8 I BalloonCanvas>drawRectangle:color:borderWidth:borderColor: >> 0x6b099c0: a(n) BalloonCanvas >> 0x24c8e8 I BalloonCanvas>fillRectangle:basicFillStyle: 0x6b099c0: a(n) >> BalloonCanvas >> >> >> Squeak: >> VM Version: Cog VM 4.0.0 (release) from Aug 22 2013 >> Compiler: gcc 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) >> Interpreter Build: CoInterpreter VMMaker.oscog-eem.331 uuid: >> 37d2e4b0-2f37-4e2d-8313-c63637785e59 Aug 22 2013 >> Cogit Build: StackToRegisterMappingCogit VMMaker.oscog-eem.333 uuid: >> 84da9cb8-7f30-4cb7-b4fb-239a11f63b54 Aug 22 2013 >> Source Version: VM: r2776 http://www.squeakvm.org/svn/squeak/branches/Cog >> Plugins: r2545 >> http://squeakvm.org/svn/squeak/trunk/platforms/Cross/plugins >> >> Current byte code: -1 >> Primitive index: 117 >> >> >> nicolai >> >> >> >> >

April 15, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by Kasper Osterbye

stepharo wrote > an idea: what about a version of FileSystem that can be used to navigate > classes? I assume there is some tooling you would like to re-use? If that is the case, I would think it would be more useful to look into what might be the right common abstraction between filesystem and class/method hierarchy - but it is hard to say without knowing the problem you were thinking of (and was it related to the text-renderer in some way I did not see?) -- Kasper -- View this message in context: http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 15, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by stepharo

Kasper an idea: what about a version of FileSystem that can be used to navigate classes? Thanks for the renderer and yes these classes suck Stef Le 15/4/15 18:27, KasperOsterbye a Ã©crit : > Thanks Damien for putting this on the mailing list. > > A few words about the state of that Pillar-TextRenderer. > > The TextRenderer accepts at least the commands shown by the screenshot noted > by Damien. In addition I would like to point to a special link type I added: > *LinkText>pharo://Classname[/methodname]* which will render a link which > when clicked will open a new Nautilus browser on said class and method. > (I think that link syntax migh actually be useful in both the HTML and Latex > Pillar exporters as well, perhaps just extracting the source and inserting > it inline in the produced document. - but perhaps that is already done using > some other feature I overlooked). > > I am rather overwhelmed by the PluggableTextView and other TextMorphs, so > please understand that the supplied functionality is most likely not the > right way to do this, but it seems to work. > > And Kilon, you are more than welcome to contact me and introduce me to this > project of yours. As new to the morphic system I can tell you that > documentation is really needed here. > > -- Kasper > > > > -- > View this message in context: http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

April 15, 2015

Re: [Pharo-dev] How to find versions of core packages?

by Peter UhnÃ¡k

There are many packages in Pharo (e.g. Spec) that don't have any explicit version outside of the commit number - because it's integrated nobody is bothered with release management (this is not a good thing but it is less work). My guess is that SUnit is in the same state. On Wed, Apr 15, 2015 at 9:09 PM, Dmitri Zagidulin <dmitri(a)zagidulin.net> wrote: > That was my first thought, too. But I couldn't find ConfigurationOfSUnit > (by any spelling) anywhere. (Not in the base image, not in the > configuration browser). And I couldn't find it in the main Pharo repo. > > There's this: http://smalltalkhub.com/#!/~SUnit/SUnit but the description > for it says 'This project is hosting the old squeaksource SUnit project.' > so I wasn't sure if that's the repo that is used for Pharo core. > > On Wed, Apr 15, 2015 at 2:46 PM, kilon alios <kilon.alios(a)gmail.com> > wrote: > >> You could take a look at the available configuration, there are usually >> version methods in the instance side like for example >> >> version10: spec >> <version: '1.0' imports: #('1.0-baseline' )> >> >> On Wed, Apr 15, 2015 at 7:24 PM, Dmitri Zagidulin <dmitri(a)zagidulin.net> >> wrote: >> >>> How does one go about finding the version numbers of core libraries like >>> SUnit that are included in a particular Pharo distribution? >>> >>> (What prompted me to try and find out is that at the start of the SUnit >>> chapter in UPBE, it says "In the future, Pharo may include version of >>> SUnit4.0." And I was curious whether Pharo 4.0 includes that newer version >>> of SUnit, etc. But I'm also curious whether there's a general procedure or >>> convention for finding versions of external libraries that are also pulled >>> into Pharo core.) >>> >> >> >

April 15, 2015

Re: [Pharo-dev] How to find versions of core packages?

by stepharo

In fact this is Sunit 3.0 or Sunit3.2 I do not think that we will have the energy to get Sunit 40. The delta is not worth the pain. Stef Le 15/4/15 18:24, Dmitri Zagidulin a Ã©crit : > How does one go about finding the version numbers of core libraries > like SUnit that are included in a particular Pharo distribution? > > (What prompted me to try and find out is that at the start of the > SUnit chapter in UPBE, it says "In the future, Pharo may include > version of SUnit4.0." And I was curious whether Pharo 4.0 includes > that newer version of SUnit, etc. But I'm also curious whether there's > a general procedure or convention for finding versions of external > libraries that are also pulled into Pharo core.)

April 15, 2015

Re: [Pharo-dev] How to find versions of core packages?

by Dmitri Zagidulin

That was my first thought, too. But I couldn't find ConfigurationOfSUnit (by any spelling) anywhere. (Not in the base image, not in the configuration browser). And I couldn't find it in the main Pharo repo. There's this: http://smalltalkhub.com/#!/~SUnit/SUnit but the description for it says 'This project is hosting the old squeaksource SUnit project.' so I wasn't sure if that's the repo that is used for Pharo core. On Wed, Apr 15, 2015 at 2:46 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > You could take a look at the available configuration, there are usually > version methods in the instance side like for example > > version10: spec > <version: '1.0' imports: #('1.0-baseline' )> > > On Wed, Apr 15, 2015 at 7:24 PM, Dmitri Zagidulin <dmitri(a)zagidulin.net> > wrote: > >> How does one go about finding the version numbers of core libraries like >> SUnit that are included in a particular Pharo distribution? >> >> (What prompted me to try and find out is that at the start of the SUnit >> chapter in UPBE, it says "In the future, Pharo may include version of >> SUnit4.0." And I was curious whether Pharo 4.0 includes that newer version >> of SUnit, etc. But I'm also curious whether there's a general procedure or >> convention for finding versions of external libraries that are also pulled >> into Pharo core.) >> > >

April 15, 2015

Re: [Pharo-dev] How to find versions of core packages?

by Peter UhnÃ¡k

I don't think it's that easy because you don't know what is loaded... so the "laborious" way would be to check monticello browser to see what commit number of a particular package is loaded, and then go through all configuration methods and see if anything matches. Maybe there is easier way but I haven't seen any. Peter On Wed, Apr 15, 2015 at 8:46 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > You could take a look at the available configuration, there are usually > version methods in the instance side like for example > > version10: spec > <version: '1.0' imports: #('1.0-baseline' )> > > On Wed, Apr 15, 2015 at 7:24 PM, Dmitri Zagidulin <dmitri(a)zagidulin.net> > wrote: > >> How does one go about finding the version numbers of core libraries like >> SUnit that are included in a particular Pharo distribution? >> >> (What prompted me to try and find out is that at the start of the SUnit >> chapter in UPBE, it says "In the future, Pharo may include version of >> SUnit4.0." And I was curious whether Pharo 4.0 includes that newer version >> of SUnit, etc. But I'm also curious whether there's a general procedure or >> convention for finding versions of external libraries that are also pulled >> into Pharo core.) >> > >

April 15, 2015

Re: [Pharo-dev] How to find versions of core packages?

by kilon alios

You could take a look at the available configuration, there are usually version methods in the instance side like for example version10: spec <version: '1.0' imports: #('1.0-baseline' )> On Wed, Apr 15, 2015 at 7:24 PM, Dmitri Zagidulin <dmitri(a)zagidulin.net> wrote: > How does one go about finding the version numbers of core libraries like > SUnit that are included in a particular Pharo distribution? > > (What prompted me to try and find out is that at the start of the SUnit > chapter in UPBE, it says "In the future, Pharo may include version of > SUnit4.0." And I was curious whether Pharo 4.0 includes that newer version > of SUnit, etc. But I'm also curious whether there's a general procedure or > convention for finding versions of external libraries that are also pulled > into Pharo core.) >

April 15, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by kilon alios

ok, but where and which repo ? Smalltalkhub ? GitHub ? Is part of Pillar ? How I install these packages ? On Wed, Apr 15, 2015 at 9:15 PM, Kasper Osterbye <kasper(a)itu.dk> wrote: > kilon.alios wrote > > So if you can provide me a link to your code, even if your code is far > > from > > final it will at least give me a good idea how things work. Suffice to > see > > I am very fresh with Morphic myself but I love to learn it, document it > > and > > improve it. > > The packages are named Pillar-TextRenderer (to be loaded first) and > Pillar-NautilusProofOfConcept (goes second). The proof of concept overrides > one method in the nautilus browser, so to go back you need to revert that > change (versions is your friend here). > > The key method in the Pillar-TextRenderer is: PRDecoratedTextWriter > class>>on: aParsedPillarDoc > > -- Kasper > > > > -- > View this message in context: > http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

April 15, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by Kasper Osterbye

kilon.alios wrote > So if you can provide me a link to your code, even if your code is far > from > final it will at least give me a good idea how things work. Suffice to see > I am very fresh with Morphic myself but I love to learn it, document it > and > improve it. The packages are named Pillar-TextRenderer (to be loaded first) and Pillar-NautilusProofOfConcept (goes second). The proof of concept overrides one method in the nautilus browser, so to go back you need to revert that change (versions is your friend here). The key method in the Pillar-TextRenderer is: PRDecoratedTextWriter class>>on: aParsedPillarDoc -- Kasper -- View this message in context: http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 15, 2015