I'm using Seaside 3.0 and Pharo 1.0 stable. Each time I get a DNU or some such from my app, the debugger fires on a WAIllegaStateException. I then have to click on Full Stack and scroll to where the actual error is. After that (abandon or fix error and proceed), I then get the UnWindException, but I can always abandon that. Happens all the time, regardless of the error.
Ok, I'll give it a try. ��Fortunately, I am not seeing it with every notifier like in the one image.
Bill
-----Original Message-----
From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Chris Muller
Sent: Monday, June 14, 2010 4:08 PM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Unwind errors: worse in 1.1?
I don't know what causees those either, but if you just want to dismiss the debugger window, try Proceed.
On Sat, Jun 12, 2010 at 5:11 PM, Schwab,Wilhelm K <bschwab@anest.ufl.edu> 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
> 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
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project