Stef, For good or bad, it appears that I can't. I have held onto the offending image in case I get any insights into what might have happened to it, but so far, I don't see how to get to the broken state.
I tried applying my build process to the core, and was stopped. I tried with the seaside 3 image and was stopped again, but noted that it had gotten far enough to try the proposed ConnectionQueue fix (2476). I added a comment to the tracker; but, rydier's suggestion of removing the ^true appears to fix it. It's hobbled now, so what do we have to lose? Bill ________________________________________ From: [email protected] [[email protected]] On Behalf Of Stéphane Ducasse [[email protected]] Sent: Sunday, June 13, 2010 3:24 AM To: [email protected] Subject: Re: [Pharo-project] Unwind errors: worse in 1.1? can you describe a scenario that we can reproduce? Stef On Jun 13, 2010, at 12:11 AM, Schwab,Wilhelm K wrote: > I have long intermittently seen errors with walkbacks titled "Unwind error > during termination." They might be more common in 1.1, and worse, I am now > unable to close the offending notifiers/debuggers. I also tried "close all > debuggers" without success. > > Bill > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
