Hi Andrey, I once made the interpreter simulator work in 3.9 and posted my changes to http://bugs.squeak.org/view.php?id=6555 In there I fixed the method that you are missing as follows: !ByteSymbol methodsFor: '*VMMaker' stamp: 'al 7/23/2007 10:17'! coerceTo: cTypeString sim: interpreter ^self! ! You may also need to check the other fixes in the Mantis issue. Please report back how it works and what changes you needed so that we can integrate what is missing in Pharo and suggest changes to David for the VMMaker package. Cheers, Adrian BTW, a stack trace is written to a file in the directory where your image is located. On Sep 5, 2009, at 19:35 , Stéphane Ducasse wrote:
I do not know the answer but this would be great to get the interpreter back on track.
Stef
On Sep 5, 2009, at 7:03 PM, Andrey Larionov wrote:
I attach screenshot of debugger to better understanding of context (why not provide in debuger an stacktrace exporter, or i miss somthing?)
On Sat, Sep 5, 2009 at 20:53, Stéphane Ducasse<stephane.ducasse@inria.fr
wrote: Let us know if you find and we need to react in pharo.
Stef
On Sep 5, 2009, at 6:16 PM, David T. Lewis wrote:
I'm sorry, I did not read your original posting carefully enough. The classes that implement coerceTo:sim: are Integer, Array, Bitmap, CArray, and CObjectAccessor. So I do not know what the problem is in this case. Sorry for the confusion.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
<Interpreter.png>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project