[Pharo-project] Unwind errors: worse in 1.1?
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
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 Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stéphane Ducasse [stephane.ducasse@inria.fr] Sent: Sunday, June 13, 2010 3:24 AM To: Pharo-project@lists.gforge.inria.fr 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 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
We will apply it. Now I'm not sure that it was working in 1.0. Stef On Jun 13, 2010, at 8:53 PM, Schwab,Wilhelm K wrote:
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: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stéphane Ducasse [stephane.ducasse@inria.fr] Sent: Sunday, June 13, 2010 3:24 AM To: Pharo-project@lists.gforge.inria.fr 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 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
Stef, Small frustration: don't integrate it. Rydier's fix breaks MC, which depends on the unfortunate semantics. I have an RC image trying to build now. In a while, I can try the fix I proposed (which changes the message loop and uses #waitForAccept* vs. #waitForConnect* when accepting), which should not break anything because it added methods rather than changing existing ones. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stéphane Ducasse Sent: Sunday, June 13, 2010 2:11 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Unwind errors: worse in 1.1? We will apply it. Now I'm not sure that it was working in 1.0. Stef On Jun 13, 2010, at 8:53 PM, Schwab,Wilhelm K wrote:
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: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stéphane Ducasse [stephane.ducasse@inria.fr] Sent: Sunday, June 13, 2010 3:24 AM To: Pharo-project@lists.gforge.inria.fr 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 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
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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
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
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. This just appeared with latest Seaside and Pharo 1.0, previous versions always fired the debugger on the point of the error. On Mon, Jun 14, 2010 at 17:14, Schwab,Wilhelm K <bschwab@anest.ufl.edu>wrote:
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
-- -JT
participants (4)
-
Chris Muller -
John Toohey -
Schwab,Wilhelm K -
Stéphane Ducasse