[Cuis-dev] Tracking down an unhandled exception

[Hernan Wilkinson]

Hi Phil,
 maybe putting a halt in the #defaultAction implementation of the
exception? That will help you see down the stack where it was signal...
also not sure if the exception is a special one, but if it is you could
also put a halt in the #signal message.

 Hope it helps!
 Hernan.

On Sun, May 17, 2020 at 12:53 PM Phil B via Cuis-dev <cuis-dev at lists.cuis.st>
wrote:

> Is it possible to find the context that an unhandled exception occurred in
> from within an #ifCurtailed: block?  I'm trying to track down such an
> exception where I suspect I've mistakenly ignored the exception in an
> #on:do: but am running out of places to look for it...
>
> Thanks,
> Phil
> --
> Cuis-dev mailing list
> Cuis-dev at lists.cuis.st
> https://lists.cuis.st/mailman/listinfo/cuis-dev
>


-- 

*Hernán WilkinsonAgile Software Development, Teaching & Coaching*
*Phone: +54-011*-4893-2057
*Twitter: @HernanWilkinson*
*site: http://www.10Pines.com <http://www.10pines.com/>*
Address: Alem 896, Floor 6, Buenos Aires, Argentina
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20200518/c82dd947/attachment.htm>