Is this reproducible then? (It is by me!) Should I report it as an issue?
Rob
I'm glad this came up, because I hit that one too and forgot about it. The other thing I have found is that more recent images are somewhat particular about the VM version - they will freeze if the (Windows is where I have seen it) vm is too old.
Bill
----
Wilhelm K. Schwab, Ph.D.
bschwab AT anest DOT ufl DOT edu
________________________________________
From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Rob Rothwell [r.j.rothwell@gmail.com]
Sent: Saturday, February 21, 2009 2:15 PM
To: Pharo-project@lists.gforge.inria.fr; dfinlayson@usgs.gov
Subject: Re: [Pharo-project] Getting started
I get that error with the new 10236 dev image as well; I don't recall getting it with the 10231 dev image. I think it is related to the initial FreeType startup process.
Start with a 10236 image, click "abandon" and close the debug window, save the image, close it, and open it again. At least I don't get the error the next time.
Rob
On Sat, Feb 21, 2009 at 12:21 PM, David Finlayson <dfinlayson@usgs.gov<mailto:dfinlayson@usgs.gov>> wrote:Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr>
What's the trick to getting a pharo image up and running?
I tried downloading the pharo-dev image 20231 from the downloads page,
then I added SqueakV39.sources from a Squeak image. When I launched I
got an error dialog saying:
Error: a primative has failed.
I was hoping to take a look around at the work you folks are doing.
--
David Finlayson
_______________________________________________
Pharo-project mailing list