[MacRuby-devel] TIL - Uncaught exceptions in threads cause SIGABRT in the main thread!

[Matt Massicotte]

If you find this exception-shifting behavior troubling, please open a ticket.

Could you explain why introducing the begin/rescue pair that is good programming practice?

Matt

On Mar 13, 2011, at 6:31 PM, Morgan Schweers wrote:

> Greetings,
> Today I Learned :) if a thread throws an exception that isn't rescued by the top of the thread, it'll crash the app's main thread with 'Program received signal:  “SIGABRT”.'
> 
> That's been plaguing me since I started doing MacRuby development; every time I tried to start up multiple threads, the app became incredibly fragile and, unlike the main thread, it wouldn't show ruby traces.
> 
> Now I just wrap threads in begin/rescue blocks, and I'm all good.  Good programming practice anyway, but the failure mode is unobvious if you don't.
> 
> Hopefully this helps someone else!
> 
> --  Morgan
> 
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20110314/dc98e003/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3737 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20110314/dc98e003/attachment.bin>