I've submitted an RFE on this rather troubling behavior. I won't restate my case, as you can just view it here: http://sourceforge.net/tracker/index.php?func=detail&aid=1274707&group_id=7586&atid=357586 Anyhow, it occurred to me that perhaps users with threads experience on other platforms (especially Windows) could comment on whether there's any similarly useful debugging behavior when exceptions are allowed to propagate outside of a thread (i.e. what the 'catch(...)' in libs/thread/src/thread.cpp:thread_proxy() specifically inhibits). If so, please update the RFE, rather than posting to the list. Matt Gruenke Software Engineer IntelliVid Corp.