On Thu, Oct 24, 2013 at 12:10 AM, Cl�ment Bera <bera.clement@gmail.com> wrote:
Ok I have the error too.Strangely enough, the error is triggered because the third BlockClosure>>#on:do: context has 2 temporaries instead of 3.�Igor / Esteban do you have a clue ? Why a context would have less temporaries than expected ? Problem from context creation out of the stack ?No. �It'll be popping too much off the stack. �See e.g. ContextPart>>jump.�I will try to find some time to look at this problem. Though it is not an easy one it will take some time to be fixed.2013/10/24 <btc@openinworld.com>
Cl�ment Bera wrote:http://files.openinworld.com/Pharo/PharoLauncher-Unwind-Error.zipHello, I'm interested. Please send me the image in private mail not to overload the mailing list with large attachment. Alternatively, give me a place where I can download it.There are three debuggers already open.� Just close them.� The third close generates the error.
The steps to reproduce are: open the image, execute 1halt, close debugger ?
A confounding factor may be your running this on a different VM.� This is mine...
http://files.openinworld.com/Pharo/PharoLauncher-Unwind-Error-VM.zip
Win32 built on Mar 13 2013 18:49:42 Compiler: 4.6.2
VMMaker versionString git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm@gmail.com> Jenkins build #14535
NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013
NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013
The error still occurs if I try the image on the latest VM, but then again the effect may already be in effect.
btw, Its not directly causing me pain since I can continue in the image, but still thanks for checking it out for general improvements.
cheers -ben
Best, 2013/10/22 <btc@openinworld.com>** For a while now, every now and then when closing a debugger I have been getting an "Unwind error during termination" I happened to have saved the image moments before it just occurred again. >From opening that save error can be reliably triggered in three clicks. I can provide this image if anyone is interested in it. cheers -ben
--
best,Eliot