On 29 oct. 2013, at 13:22, Clément Bera wrote:
> (Igor speaking with Clement) Another, tangent.
>
> I feel extremely wrong with given piece of code (however it works):
>
> [ ^ 2 ] ensure: [ ^ 5 ]
>
> my point, that you cannot return from same context twice, and what happens
> here is real
(Igor speaking with Clement) Another, tangent.
I feel extremely wrong with given piece of code (however it works):
[ ^ 2 ] ensure: [ ^ 5 ]
my point, that you cannot return from same context twice, and what happens
here is really weird.
Or even more weird:
[ ^ 2 ] ifCurtailed: [ ^ 5 ]
or
If I remember correctly andreas wrote the tests.
I always like them.
Stef
> The author of the test is Andreas Raab, but I'm not sure who found it
> (excavating mailing list is hard work)
>
>
> 2013/10/25 Igor Stasenko
>
>
>
> On 25 October 2013 00:26, Nicolas Cellier
> wrote:
> Hard to
On 25 October 2013 01:28, Nicolas Cellier <
nicolas.cellier.aka.n...@gmail.com> wrote:
> The author of the test is Andreas Raab, but I'm not sure who found it
> (excavating mailing list is hard work)
>
> and this test is missing in pharo, so thanks anyways :)
i can't imagine what can't go wrong i
The author of the test is Andreas Raab, but I'm not sure who found it
(excavating mailing list is hard work)
2013/10/25 Igor Stasenko
>
>
>
> On 25 October 2013 00:26, Nicolas Cellier <
> nicolas.cellier.aka.n...@gmail.com> wrote:
>
>> Hard to debug this kind of code :(
>> This is reproducible
On 25 October 2013 00:26, Nicolas Cellier <
nicolas.cellier.aka.n...@gmail.com> wrote:
> Hard to debug this kind of code :(
> This is reproducible on Squeak wiht on:do:, so on:fork: bizareness apart,
> this is another flaw in exception handling, along with wrong handler for
> nested exception (tes
Hard to debug this kind of code :(
This is reproducible on Squeak wiht on:do:, so on:fork: bizareness apart,
this is another flaw in exception handling, along with wrong handler for
nested exception (testHandlerFromAction below), unless it's an avatar.
Still, I do not see how you get the errorSubs
ok, it seems i found how to reproduce the situation with following:
[ [ 1/0 ] ensure: [ nil foo ] ] on: Error fork: [ :ex | 1halt ]
you will get halt, and if you close the debugger , it will throw unwind
error.
(while instead it should throw DNU)
--
Best regards,
Igor Stasenko.
the stack looks quite strange..
but if you open the debugger on that unwind error and see the
#resume:
context, evaluating:
self isDead yields to true.
it is a mystery however, how #resume: end up on the stack,
when you just closing the debugger window and terminating the process.
it seems like th
I doubt that the reason is some bug in VM,
i suspecting much simpler explanation:
if you look at the bottom of stack, it starts from on:fork:
it tries to deliver announcement.. and everything goes well until it gets
an exception:
PharoLauncher class(Object)>>doesNotUnderstand: #quitOnLaunch
the
On Thu, Oct 24, 2013 at 11:25 AM, Clément Bera wrote:
> OK I'll wait for another use case or until it happened to me. Like a
> usecase from a fresh image.
>
> It's just it may be due to the new inspector, new debugger or new
> compiler. Just wondering.
>
It's definitely not due to the new code.
OK I'll wait for another use case or until it happened to me. Like a
usecase from a fresh image.
It's just it may be due to the new inspector, new debugger or new compiler.
Just wondering.
2013/10/24 Eliot Miranda
>
>
>
> On Thu, Oct 24, 2013 at 12:10 AM, Clément Bera wrote:
>
>> Ok I have the
On Thu, Oct 24, 2013 at 12:10 AM, Clément Bera 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 e
Le 24/10/2013 16:28, b...@openinworld.com a écrit :
Clément Bera 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
temporar
Clément Bera 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
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 ?
I will
Clément Bera wrote:
Hello,
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.
http://files.openinworld.com/Pharo/PharoLauncher-Unwind-Error.zip
The steps to reprodu
Hello,
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.
The steps to reproduce are: open the image, execute 1halt, close debugger ?
Best,
2013/10/22
> **
> For a while no
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
19 matches
Mail list logo
