[Pharo-project] latest build yields stack trace running #cleanUpForProduction
stephane.ducasse at inria.fr
Tue Jan 17 22:18:29 CET 2012
open a bug entry. We got some strange behavior with becomeForward: and set rehash and I wonder if this is not related.
On Jan 17, 2012, at 10:03 PM, Yanni Chiu wrote:
> Using Pharo 1.4 (#220), I end up in:
> ByteSymbol(Object)>>doesNotUnderstand: #run:with:in:
> which was called from:
> (MCPackage named: self theScriptLoaderPackageName) unload.
> First I thought it was because I had OSProcess loaded when I ran cleanUpForProduction, and it stopped in an OSProcess class.
> Without OSProcess, the I got a slightly different problem: the doesNotUnderstand of #run:with:in: is due to something in #cleanUpForRelease. Trying to debug it, new debuggers pop up, and then the emergency evaluator.
> I have Seaside30/Magritte/Pier loaded, so I can try without those too. But, it used to work with all these things loaded.
More information about the Pharo-project