I have a solution however! Each timer on the run loop runs its action in a fork. This way any exception raised cannot unroll the stack to outside my run loop code.
On 7 Sep 2012, at 12:24, Joe Rickerby <[email protected]> wrote: > Not really. Proceed would take me back to where the exception was signalled. > I want to resume at the point of the catch of the exception, no matter what > happens regarding the exception. > > On 7 Sep 2012, at 09:40, Henrik Sperre Johansen > <[email protected]> wrote: > >> On 07.09.2012 10:17, Joe Rickerby wrote: >>> Hi all, >>> >>> I'm having a problem trying to build a run loop. If an exception is >>> signalled within one of the run loop tasks, the exception escapes through >>> the loop and terminates the process. >>> >>> I know I can catch the exception, and do something like print the message >>> on the Transcript, but I was hoping to build something that was more >>> helpful in development, allowing me to look through the stack, but if I >>> press 'abandon' on that dialog, the run loop would continue from where I >>> caught the exception. >>> >>> >> Isn't that exactly what happens if you don't handle the error, and use the >> proceed button in (pre and normal) debugger windows? >> >> Cheers, >> Henry >
