- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3806 in pharo: Duration>>hours is broken
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Status: New Owner: ---- New issue 3806 by sebastia...(a)gmail.com: Duration>>hours is broken http://code.google.com/p/pharo/issues/detail?id=3806 Steps to reproduce: 1. self assert: 2 days hours = 48 2. do 3. it it will fail It's a bug because of what is said in the comment. But please don't even think in fixing it by changing the comment. Even a toddler would expect to see 48 hours in a duration of two days. BTW: I've just saw this and I'm probably going to make a patch

5 20

Re: [Pharo-project] Issue 3714 in pharo: ChangeSet removeSelector does not dirty packages
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Updates: Summary: ChangeSet removeSelector does not dirty packages Comment #2 on issue 3714 by stephane...(a)gmail.com: ChangeSet removeSelector does not dirty packages http://code.google.com/p/pharo/issues/detail?id=3714 (No comment was entered for this change.)

1 1

[Pharo-project] [update 1.3] #13102
by StÃ©phane Ducasse March 22, 2011

March 22, 2011

13102 ----- - Cleaning Polymorph overrides. Part two. Stef

1 0

[Pharo-project] [update 1.3] #13101
by stephane ducasse March 22, 2011

March 22, 2011

13101 ----- - Cleaning Polymorph overrides. Part one

1 0

Re: [Pharo-project] test crashing the cog vm
by Marcus Denker March 22, 2011

March 22, 2011

On Mar 22, 2011, at 1:35 PM, StÃ©phane Ducasse wrote: > But why we could not have a byecode validator at the image level that first make sure that byte code are in sync with the format of the objects. > Why this has to be done in the vm. > Because you can not gurantee that they are not changed after. Or that the code is changed that does the checking. or... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Getting a functionning unstable image
by Marcus Denker March 22, 2011

March 22, 2011

On Mar 21, 2011, at 11:19 PM, Nicolas Cellier wrote: > > > So it was my fault finally: it's because I was too early, and started > from Pharo0.x, then applied this automated condenseSources: > Oh. > > That explains why I can never upgrade from a newer image... > I brought my 0.x image up to 1.2 by some tricky manual MC loading > and/or selective loading. > But now, things shall be easier :) > Yes... the thing is that everythign that we do not test will not work. We do not test updating 0.x --> 1.2. It *will* be broken. (And there is the question if it makes sense to keep these things working. I vote for investing into a declarative bootstrap instead, far more important) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

Re: [Pharo-project] test crashing the cog vm
by Marcus Denker March 22, 2011

March 22, 2011

On Mar 22, 2011, at 12:17 AM, Toon Verwaest wrote: > >> On Mon, Mar 21, 2011 at 7:23 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> This would be a nice little topic... this bytecode verifier. >> >> Probably on top of Opal >> >> The bytecode verifier must be in the VM. If it is up in the image it can be side-stepped. The VM is the ultimate executor of code and so it must apply verification. It could be written in Smalltalk and verified in Smalltalk and then translated. But it must be part of the VM and used by the VM before running any previously unverified method. >> >> best, >> Eliot > Indeed, Mariano's response made me want to scream: NOOOOO! :) > > HOWEVER!, Thinking about it now, it's actually a very interesting proposal! What if we write this piece of software in Smalltak and give it to the VM as part of the VM definition. The VM decides what the application can see, so it might as well not give access to this smalltalk-written bytecode validator that it knows to be safe. If it's built by a separate classbuilder in a separate environment, it can be clearly separated, invulnerable to become: and other evil-doing. So, in short. It's written in Smalltalk (YAY!), but becomes part of the VM runtime, not of the image running on the VM. If we just make sure that we can write out image segments that the VM can use as part of its core (exactly what I do in Pinocchio incidentally), we can just develop and test it nicely in Pharo. Ain't that super-duper cool? > If we would have solved the security problem already, then we could use it for the bytecode verifyer, too... (guarantee that nobody tampers with the verifyer). We need to reify that was makes "the VM" special and provide it for all smalltalk code. But that is of course research and completely not clear yet what it means. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Getting a functionning unstable image
by Nicolas Cellier March 22, 2011

March 22, 2011

Hi guys, Updating Pharo from the update stream failed many times and keep on failing for me... But maybe it's just me... So I picked the unstable link from the web site (http://www.pharo-project.org/pharo-download/unstable-core) This drives me to a 13091 image. The first thing I do is select the 'update system' menu... Err, it fails... It seems related to broken sources... Well the image points to which source file ? can't remember the incantation, let just browse it... Err, no source, I can't browse. No matter, I set the browser to decompile mode... Err, this does not work, I still can't browse code. Hmm very bad starting experience, I know what unstable means, but I was dreaming of other words like continuous development. So ket's open an older image (my own updated 1.2) to find the incantations. (Scanner>>#scanTokens:) fileIndex -> 1, so it seems that the source file is corrupted. (SourceFiles at: 1) -> MultiByteFileStream: '/Users/nicolas/Smalltalk/Squeak/pharo/PharoV10.sources' Well, for my previous Pharo images, this very file works ! How damned can be the file be changed and the version not incremented ? Is it me who did something wrong ? Or the update process somewhere did condense the sources ? Or did someone elese messed with the sources ? Is it a known problem ? Any help appreciated. Nicolas

2 4

Re: [Pharo-project] Security Vunerability in SqueakSource
by Marcus Denker March 21, 2011

March 21, 2011

On Mar 21, 2011, at 3:24 AM, Matthew Fulmer wrote: > As demonstrated by the VMMaker team, SqueakSource has a rather > serious security vunerability: > Serious security problems are normally send to the admins of a website first (so they fix it) instead of sending it to a mailinglist... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

Re: [Pharo-project] Getting a functionning unstable image
by Marcus Denker March 21, 2011

March 21, 2011

Hello, > Hi guys, > Updating Pharo from the update stream failed many times and keep on > failing for me... > But maybe it's just me... > Updating never failied for me... (Hudson not,either). (e.g. I can download the 13091 and it updates without error) > So I picked the unstable link from the web site > (http://www.pharo-project.org/pharo-download/unstable-core) > This drives me to a 13091 image. > The first thing I do is select the 'update system' menu... > Err, it fails... It seems related to broken sources... > Well the image points to which source file ? can't remember the > incantation, let just browse it... > Err, no source, I can't browse. > No matter, I set the browser to decompile mode... > Err, this does not work, I still can't browse code. > Hmm very bad starting experience, I know what unstable means, but I > was dreaming of other words like continuous development. > I have not seen that problem... I will investigate. > So ket's open an older image (my own updated 1.2) to find the incantations. > (Scanner>>#scanTokens:) fileIndex -> 1, so it seems that the source > file is corrupted. > (SourceFiles at: 1) -> MultiByteFileStream: > '/Users/nicolas/Smalltalk/Squeak/pharo/PharoV10.sources' > > Well, for my previous Pharo images, this very file works ! > How damned can be the file be changed and the version not incremented ? > It should not be changed. > Is it me who did something wrong ? > Or the update process somewhere did condense the sources ? I hope not! > Or did someone elese messed with the sources ? > Is it a known problem ? > With Igor we saw some problem when decompiling code. (remove sources). What we should do, too is to invest into the regression tester to acutally test things like if the changes and sources are in a good shape, if we can condense, write new sources, all these things... -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0