[Pharo-project] latest build yields stack trace running #cleanUpForProduction

Mariano Martinez Peck marianopeck at gmail.com
Tue Jan 17 16:44:55 EST 2012


I have already opened an issue several months ago:
http://code.google.com/p/pharo/issues/detail?id=5005

I have also made it as much reproducable as I could and I have also asked
for help:
http://forum.world.st/Help-with-cleanUpForRelease-is-broken-MessageNotUnderstood-ByteSymbol-run-with-in-tp4205909p4205909.html

No answers :(

Cheers

On Tue, Jan 17, 2012 at 10:18 PM, Stéphane Ducasse <
stephane.ducasse at inria.fr> wrote:

> Hi Yanni
>
> open a bug entry. We got some strange behavior with becomeForward: and set
> rehash and I wonder if this is not related.
>
> stef
>
> 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.
> >
> > --
> > Yanni
> >
> >
>
>
>


-- 
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20120117/a312dc68/attachment-0001.html>


More information about the Pharo-dev mailing list