[Glass] Problem with UncontinuableError

Dale Henrichs dale.henrichs at gemtalksystems.com
Mon Mar 10 09:33:17 PDT 2014


What message are you sending to trigger the exception and what does the
stack look like?

Dale


On Mon, Mar 10, 2014 at 7:40 AM, Mariano Martinez Peck <
marianopeck at gmail.com> wrote:

> Hi guys,
>
> At some place in code, I am storing exceptions when they happen inside a
> collection. Basically I have a #on:do:  and I store the error in a
> collection. And then I do something (printing basically).
> I have a strange behavior in GemStone in comparison to Pharo. In Pharo, I
> would get the original normal print string of the real exception that
> happened. In GemStone, instead of getting the original exception I get this:
>
> a UncontinuableError occurred (error 6011), Execution cannot be continued,
> 'Exception has already been signaled'
>
> Any idea what is happening?
>
> Thanks in advance,
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20140310/55a35e94/attachment.html>


More information about the Glass mailing list