Igor Peshansky wrote: > I've looked at this a bit. Here's the weird part: the error says > "Uncaught Exception", but all the throws of that exception appear to be > properly wrapped in try/catch blocks. So a simple "change exception into > an mbox" kind of solution won't work here. More debugging is needed.
The reason for the box is that the md5 checking was changed to run in a different thread than originally designed (now in the main thread instead of the download thread IIRC) and that thread does not have any particular catch handler for that exception, only the TOPLEVEL_CATCH which punts with the generic error. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
