On Mar 13, 2013, at 7:11 PM, Eliot Miranda eliot.mira...@gmail.com wrote:
On Tue, Mar 12, 2013 at 7:54 PM, Igor Stasenko siguc...@gmail.com wrote:
On 12 March 2013 19:44, Eliot Miranda eliot.mira...@gmail.com wrote:
3. Pharo has forked the VM to include a) NativeBoost and b)
On Thu, Mar 14, 2013 at 7:20 AM, Esteban Lorenzano esteba...@gmail.comwrote:
On Mar 13, 2013, at 7:11 PM, Eliot Miranda eliot.mira...@gmail.com
wrote:
On Tue, Mar 12, 2013 at 7:54 PM, Igor Stasenko siguc...@gmail.com wrote:
On 12 March 2013 19:44, Eliot Miranda eliot.mira...@gmail.com
On 14 March 2013 19:01, Eliot Miranda eliot.mira...@gmail.com wrote:
Yes. RTL is essentially an assembler for an abstract machine with readable
names for registers. Arguably the Cog back-end assembler is an RTL. It has
abstract registers (ReceiverResultReg, ClassReg etc), and abstract
On Tue, Mar 12, 2013 at 7:54 PM, Igor Stasenko siguc...@gmail.com wrote:
On 12 March 2013 19:44, Eliot Miranda eliot.mira...@gmail.com wrote:
3. Pharo has forked the VM to include a) NativeBoost and b) ephemerons
and
c) new FileSystem primitives.
a) is cool, but I don't like the x86
Great.
Is there anything I can do to help fixing the problem? (my problem is that
I do not even know where to start)
As you can imagine this is an important blocker for the Moose team.
Cheers,
Doru
On Mon, Mar 11, 2013 at 9:58 PM, stephane ducasse
stephane.duca...@free.frwrote:
thanks
Hi Doru,
We are working hard to try to fix the vm stability issues and users help is the
only way we can have enough crash cases to debug.
Sending a mail to the list with a reproducible case is the best way to help up
fix the vm.
Any report is welcomed :)
Esteban
On Mar 12, 2013, at 9:20
I do not understand. I sent the mail with a reproducible case twice (one is
just below) :)
Is this enough? Could you reproduce it?
Doru
On Tue, Mar 12, 2013 at 9:36 AM, Esteban Lorenzano esteba...@gmail.comwrote:
Hi Doru,
We are working hard to try to fix the vm stability issues and users
I will try it today :)
On Mar 12, 2013, at 9:38 AM, Tudor Girba tu...@tudorgirba.com wrote:
I do not understand. I sent the mail with a reproducible case twice (one is
just below) :)
Is this enough? Could you reproduce it?
Doru
On Tue, Mar 12, 2013 at 9:36 AM, Esteban Lorenzano
Doru
You cannot expect people to work when there are on vacation :).
BTW I only saw the second report.
In addition this is why we are building the consortium because our team will
not be able to pay one full time engineer in the long
run.
Many people do not get that this is not granted that
It would be good to have a parallel job, but the problem is that you will
get a message saying that the VM is too old for the Pharo 2.0 image.
I started the latest MOOSE image on Eliots latest VM on mac.
It still has the 'old vm' warning.
Adding a monticello repository (directory) doesn't work.
Hi Stef,
I do not assume that people have to work on my bug reports.
I simply clarified the confusion: Esteban was asking for a reproducible
case and the reproducible steps were right below his email :).
Btw, you even replied to the first report, but I should have made the title
more clear :)
Eliot builds will always have the old vm warning, even if they are not old
:)...
you need one of the pharo builds (CogVM, NBCogVM or PharoVM)
On Mar 12, 2013, at 10:05 AM, Stephan Eggermont step...@stack.nl wrote:
It would be good to have a parallel job, but the problem is that you will
get
Hi Stef,
I do not assume that people have to work on my bug reports.
I simply clarified the confusion: Esteban was asking for a reproducible case
and the reproducible steps were right below his email :).
Btw, you even replied to the first report, but I should have made the title
Eliot's VMs on Mac will always give the warning as the version isn't
the same kind of string as Esteban's. Some kind of git thing, like:
#define REVISION_STRING git://gitorious.org/cogvm/blessed.git Commit:
63aa6ed8a070fc730224b496e0dda7c3f8482e10 Date: 2013-02-14 11:43:21
+0100 By: Esteban
Esteban wrote:
Eliot builds will always have the old vm warning, even if they are not old
:)...
you need one of the pharo builds (CogVM, NBCogVM or PharoVM)
Well, Doru reported they crashed. Eliot's one doesn't:
15875 run, 15472 passes, 2 skipped, 88 expected failures, 216 failures, 99
Eliot as a new VM as of yesterday
http://www.mirandabanda.org/files/Cog/VM/VM.r2701/README.2701
That kind of fixes things.
But I guess the Pharo team still has to integrate these fixes.
BTW, here is the version string from the Cog VM explaining the too
old message:
Smalltalk vm version.
We use an automated building method that tries to be exactly the same in each
platform. We decided not to create bundles but dylibs because bundles are
mac-specific stuff and .dylibs same (but for mac) as .so and .dll.
Our process builds the vm, the plugins and the third party libraries as an
Thank you very much. It makes a lot of sense doing things the Pharo way.
Now, I have been trying to get the InterpreterSimulator to work in
Pharo but there are some things to fix before being able to do so (one
is to have an image in 6504 format but hey, this is for me learning)
Classes like
Phil wrote:
Eliot as a new VM as of yesterday
http://www.mirandabanda.org/files/Cog/VM/VM.r2701/README.2701
That kind of fixes things.
But I guess the Pharo team still has to integrate these fixes.
This is with 2701. The Moose image is based on Pharo 20589
Stephan
Also, it looks like the Pharo VM uses only external plugins? The
Squeak VM has a bunch of those plugins, but as internal ones. That's
probably most of the difference Phil's asking about.
frank
On 12 March 2013 09:57, Esteban Lorenzano esteba...@gmail.com wrote:
We use an automated building
not exactly, but yes, some of the plugins that are internal in Eliot's are
external for pharo (no real important reason: we decided to put as external as
many as possible :)
Esteban
On Mar 12, 2013, at 11:15 AM, Frank Shearar frank.shea...@gmail.com wrote:
Also, it looks like the Pharo VM
On Mar 12, 2013, at 11:02 AM, p...@highoctane.be wrote:
Thank you very much. It makes a lot of sense doing things the Pharo way.
Now, I have been trying to get the InterpreterSimulator to work in
Pharo but there are some things to fix before being able to do so (one
is to have an image in
by base Interpreter you mean an InterpreterVM?
On Mar 12, 2013, at 11:02 AM, p...@highoctane.be p...@highoctane.be wrote:
Thank you very much. It makes a lot of sense doing things the Pharo way.
Now, I have been trying to get the InterpreterSimulator to work in
Pharo but there are some
The iOS VM has another layout even. And the exe is smaller than 600KB.
Phil
2013/3/12 Esteban Lorenzano esteba...@gmail.com:
not exactly, but yes, some of the plugins that are internal in Eliot's are
external for pharo (no real important reason: we decided to put as external
as many as
The Utilities thing is just used to display a progress dialog
inform:during:, so that's easy. Also String asText form for Display
can be solved with a blank form.
I am now stuck on getting a 6504 image format.
Phil
2013/3/12 stephane ducasse stephane.duca...@free.fr:
On Mar 12, 2013, at 11:02
No, I mean:
(InterpreterSimulator initializeWithOptions: Dictionary new).
(InterpreterSimulator new openOn: Smalltalk imageName) test.
working.
Of course, this does the trick on its own image, so, I could be happy
enough with whichever image can be used there.
That's in an image with VMMaker
the layout for iOS apps is very different than for OSX apps... that's why iOS
has a different arrangement.
- also, apple does not allows dynamic links for iOS, so every included plugin
has to be internal.
- also, we are not including many of the plugins (those who does not has sense
in iOS, or
Hi:
On 12 Mar 2013, at 11:43, p...@highoctane.be wrote:
The Utilities thing is just used to display a progress dialog
inform:during:, so that's easy. Also String asText form for Display
can be solved with a blank form.
Some of that has been reported last year, including patches:
I didn't noticed them until now... I will integrate them as soon as possible :)
Esteban
On Mar 12, 2013, at 12:33 PM, Stefan Marr smallt...@stefan-marr.de wrote:
Hi:
On 12 Mar 2013, at 11:43, p...@highoctane.be wrote:
The Utilities thing is just used to display a progress dialog
On 12 March 2013 10:43, p...@highoctane.be p...@highoctane.be wrote:
The Utilities thing is just used to display a progress dialog
inform:during:, so that's easy. Also String asText form for Display
can be solved with a blank form.
I am now stuck on getting a 6504 image format.
What are you
On 12 March 2013 10:49, p...@highoctane.be p...@highoctane.be wrote:
Eliot's CogVM vs PharoVM on Mac application contents. Quite different.
And worth some explanations :-) Why is it that way?
There was a discussion about that in dev list, and decision was made.
First thing, putting external
On Tue, Mar 12, 2013 at 2:57 AM, Esteban Lorenzano esteba...@gmail.comwrote:
We use an automated building method that tries to be exactly the same in
each platform. We decided not to create bundles but dylibs because bundles
are mac-specific stuff and .dylibs same (but for mac) as .so and
Thanks a lot all to all of you for that valuable information.
BTW, there is no pure PharoInterpreterVM available anywhere. And the
InterpeterVM Frank mentioned is only available in Unix, not in OSX.
(this for learning with the InterpreterSimulator in VMMaker packages)
From a personal POV, I like
On Mar 12, 2013, at 7:44 PM, Eliot Miranda eliot.mira...@gmail.com wrote:
On Tue, Mar 12, 2013 at 2:57 AM, Esteban Lorenzano esteba...@gmail.com
wrote:
We use an automated building method that tries to be exactly the same in each
platform. We decided not to create bundles but dylibs
On 12 March 2013 18:55, p...@highoctane.be p...@highoctane.be wrote:
Thanks a lot all to all of you for that valuable information.
BTW, there is no pure PharoInterpreterVM available anywhere. And the
InterpeterVM Frank mentioned is only available in Unix, not in OSX.
(this for learning with
On Tue, Mar 12, 2013 at 12:01 PM, Esteban Lorenzano esteba...@gmail.comwrote:
On Mar 12, 2013, at 7:44 PM, Eliot Miranda eliot.mira...@gmail.com
wrote:
On Tue, Mar 12, 2013 at 2:57 AM, Esteban Lorenzano esteba...@gmail.comwrote:
We use an automated building method that tries to be
On 12 March 2013 19:44, Eliot Miranda eliot.mira...@gmail.com wrote:
3. Pharo has forked the VM to include a) NativeBoost and b) ephemerons and
c) new FileSystem primitives.
a) is cool, but I don't like the x86 specificity. I want a cross-platform
FFI, so I'm not excited enough to include
Hi,
Where should I report Pharo VM crashes with Pharo 2.0?
In particular, I wanted to report the problem related to running Moose tests
from the command line:
---
You can reproduce it on Mac, quite consistently: just run the attached script
(you need to have wget installed), or do it
thanks doru!
Hi,
Where should I report Pharo VM crashes with Pharo 2.0?
here first :)
In particular, I wanted to report the problem related to running Moose tests
from the command line:
---
You can reproduce it on Mac, quite consistently: just run the attached script
(you need
39 matches
Mail list logo
